Hi, i'm stuck on TWRP 2.8.7.1 after a failed attempts to update LineageOS via OTA.
I cannot boot in bootloader nor in system, it always shows TWRP.
I found everywhere that in this case you should use these command lines :
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
but it gives me "no such file or directory" error :
Code:
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/fota': No such file or directory
~ # ls /dev/block/platform/
7824900.sdhci 7864900.sdhci
These are the only files I have in /dev/block/platform/
I don't know why but I can't update TWRP via TWRP : when I try to flash the image it just proposes me to flash the boot partition (not the recovery).
What could I do ?
I forgot to mention I flashed the correct crackling LineageOS image afterward, and it worked, but I'm still blocked in TWRP.
I handled it !
I just changed the command line to :
Code:
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/fota
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/misc
Too bad I completely wiped all my phone trying to make things work. I hope it will be useful to someone !
Hello, same twrp loop with 3.0.0 or brick with twrp 3.0.3 by fastboot
I find "fastboot continue" to boot in system
I'm testing with last nightly,
after update twrp with playstore
krodelabestiole said:
I handled it !
I just changed the command line to :
Code:
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/fota
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/misc
Too bad I completely wiped all my phone trying to make things work. I hope it will be useful to someone !
Click to expand...
Click to collapse
This just saved my son's phone
Thanks for your message and knowledge on this matter. The force salutes you and is with you
I keep coming to this thread for the commands.
Thanks krodelabestiole
krodelabestiole said:
I handled it !
I just changed the command line to :
Code:
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/fota
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/misc
Too bad I completely wiped all my phone trying to make things work. I hope it will be useful to someone !
Click to expand...
Click to collapse
This finally saved me. I was trying the same two commands that you started with and got the same "no such directory..." error and your new commands worked. That was a tense few hours.
Related
I would like to try flashing the stock bell rom back on my phone but I never backed it up initially.
I've been having Bluetooth music issues with both kernelpanics and ho!no!s roms so I have to get stock to test if its the phone or just the roms while its still in warranty.
Thanks guys!!
Sent from my LG-P930 using XDA
EDIT:
Found stock system.img
What are the ADB commands to flash the file to my phone?
Bump for new topic. Found System.img of stock bell canada rom
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
Epyoch said:
adb shell
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
Click to expand...
Click to collapse
when I type SU in, it says /sbin/sh: su: not found
and if i try dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
it gives me dd: can't open '/sdcard/system.img': No such file or directory
Okay, first, in CWM, you don't need to su for root permissions, your ADB shell has them. Second, if you haven't copied your file to the root level of your sdcard and if your file isn't named "system.img" exactly, that command will fail. I'll leave it to you to figure out how to move/rename your system.img file accordingly lol
Edit, it just occurred to me you might be having the garbled sdcard problem where it will spit out garbage if you type in the "ls" command in ADB. The solution has been posted by kernelpan1c, but first let us know what the output of ls is if you're sure your system.img is in the root level of your sdcard.
Malnilion said:
Okay, first, in CWM, you don't need to su for root permissions, your ADB shell has them. Second, if you haven't copied your file to the root level of your sdcard and if your file isn't named "system.img" exactly, that command will fail. I'll leave it to you to figure out how to move/rename your system.img file accordingly lol
Edit, it just occurred to me you might be having the garbled sdcard problem where it will spit out garbage if you type in the "ls" command in ADB. The solution has been posted by kernelpan1c, but first let us know what the output of ls is if you're sure your system.img is in the root level of your sdcard.
Click to expand...
Click to collapse
I already used ADB to push system.img to my phone's SDCard root directory.
Are you suggesting that I reformat my SDCard through windows?
I just realized that I am lacking the boot.img of the stock bell ROM. system and boot are the two that are absolutely necessary to get the phone working correct?
Which rom are you coming from? If it's a Nitro rom/kernelpan1c's rom, you shouldn't have to flash boot.img.
Yeah, according to kernelpan1c, there is something weird going on with the way our sdcard is formatted. After formatting it in Windows he says it should work just fine in the CWM flashed by Rom Manager (I haven't tested it myself, but I'm sure he's correct). I really want to know what is making the Rom Manager CWM unable to read it where bytecode64's CWM can read it just fine...
Malnilion said:
Which rom are you coming from? If it's a Nitro rom/kernelpan1c's rom, you shouldn't have to flash boot.img.
Yeah, according to kernelpan1c, there is something weird going on with the way our sdcard is formatted. After formatting it in Windows he says it should work just fine in the CWM flashed by Rom Manager (I haven't tested it myself, but I'm sure he's correct). I really want to know what is making the Rom Manager CWM unable to read it where bytecode64's CWM can read it just fine...
Click to expand...
Click to collapse
I think I'll be using HO!NO!'s rom as a base for the boot.img, since he has a bell optimus LTE, not the AT&T phone. I'm assuming that he hasn't made any changes to the boot partition, since no custom kernel development has occurred for this phone yet.
I found a so called legit CWM backup of the BELL rom, in one of the lu6200 threads, http://forum.xda-developers.com/showthread.php?t=1472501
but recovering the backup only hangs on the LG logo. I did a "advanced restore" and restored only the system and boot files but that didn't get past the logo either...
It booted after an advanced restore with the "stock" system(from that thread) and the boot (from HONO's), but the WIFI wouldn't start, it said error.
Where did you get your stock bell system.img? and can you provide it?
hereric said:
when I type SU in, it says /sbin/sh: su: not found
and if i try dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
it gives me dd: can't open '/sdcard/system.img': No such file or directory
Click to expand...
Click to collapse
Mount sdcard in recovery.
After you enter adb shell
"mount /sdcard" (without quotations)
Then use the command "dd if=/sdcard/system.img of=/dev/block/mmcblk0p27"
First of all I'm still exploring Androide and Linux = bit of a noob still
I rooted and then saved those images like this:
dd if=/dev/block/mmcblk0p10 of=/storage/extSdCard/backup/recovery/recovery_dd.img
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/backup/efs/efs_dd.img
How can I restore them ?? (via ADB, Odin, Flashify)
In the opposite way
dd if=/storage/extSdCard/backup/recovery/recovery_dd.img of=/dev/block/mmcblk0p10
dd if=/storage/extSdCard/backup/efs/efs_dd.img of=/dev/block/mmcblk0p3
radkor said:
In the opposite way
dd if=/storage/extSdCard/backup/recovery/recovery_dd.img of=/dev/block/mmcblk0p10
dd if=/storage/extSdCard/backup/efs/efs_dd.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
THX, didnt know that it is that simple. Can this be done during the device is in normal ON mode or do I have to set the device into a special mode after boot ?
How would you restare a system.img made with dd ? (I think ist not such a good idea to do it in normal ON mode ??)
How would you restore a system.img ?
a) extracted from StockROM package (does it need any conversion first ?)
b) made with dd
I think ist might not be a good idea to do it in normal ON mode ?? (Odin, ....???)
I have sphinx 1.5 on my lg f240. TWRP version is 2.3.6.0.
I factory reset my phone and I am stuck in TWRP boot loop i.e everytime phone restarts, it open TWRP.
I posted on xda forums and someone gave me a file to install. I put that file on SD card but the problem is that in install option, i cant see sd card.
I have tried this command in terminal
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
as recommended on http://forum.xda-developers.com/showpost.php?p=48136185&postcount=268
Also tried this command
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
But no effect.
Now I cant install anything as i dont have access to SD card. What to do now?
Finally this command in terminal of TWRP worked for me. yayyyyy
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
First of all! it takes some time! so don't despair at first try.
--- We will install the kingroot.net (APK) and of course type *#0808# and select the last option.
--- at this time the phone will reboot. (it should be connected to a wifi)
--- start the kingroot app and let it work
--- while kingroot is working we will start an adb session with command "adb shell"
--- when The process in phone is at 30% type "su" in adb session
--- once with root permission we are going to type these line of commands one over one the fastest you can.
"dd if=/dev/zero of=/dev/block/mmcblk0p" after the "..0p" type first 10, later 13, 14, 15 and 16.
Example:
dd if=/dev/zero of=/dev/block/mmcblk0p10 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p13 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p14 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p15 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p16 (enter line)
--- every time you enter a line the adb session will popup the message "fail to write no space" or something like that. DON'T WORRY keep typing.
--- At the end of this the phone will reboot for the bootloop but when it boots will show signal and "emergency calls only" message.
--- If you check in Bsaeband will say the right number and no "unknown"
--- Now thanks to Octopus box and their certs support! Write the new cert
--- Everything OK! Phone working and unlocked!
If you want to push thanks I'm okay I should upload images but i was so scared with the phone so I decide to not move anymore xD
If you want to Donate! even a cent! it's good paypal. com /cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=9MJHWHVJW3S94
What is it unlocking?
It has already been available for some time. Credits goes to Bisco, at forum.gsmhosting.com/
---------- Post added at 09:54 PM ---------- Previous post was at 09:48 PM ----------
dallen5 said:
What is it unlocking?
Click to expand...
Click to collapse
No, it just fixes the boot-loop due to a corrupted baseband. You will have to wipe the EFS partition and reset the MSL with a box that supports the features; Z3X, Octoplus, Etc... Then, write the cert file in order to get the network functioning.
this is cool.
could you write a .bat file to just run this operation automatically rather than having to type really fast?
(fyi - my baseband is fine. i was just curious if a .bat file would work as it might be helpful to anyone needing to utilize this method.)
step process
rondoo said:
First of all! it takes some time! so don't despair at first try.
--- We will install the kingroot.net (APK) and of course type *#0808# and select the last option.
--- at this time the phone will reboot. (it should be connected to a wifi)
--- start the kingroot app and let it work
--- while kingroot is working we will start an adb session with command "adb shell"
--- when The process in phone is at 30% type "su" in adb session
--- once with root permission we are going to type these line of commands one over one the fastest you can.
"dd if=/dev/zero of=/dev/block/mmcblk0p" after the "..0p" type first 10, later 13, 14, 15 and 16.
Example:
dd if=/dev/zero of=/dev/block/mmcblk0p10 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p13 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p14 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p15 (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p16 (enter line)
--- every time you enter a line the adb session will popup the message "fail to write no space" or something like that. DON'T WORRY keep typing.
--- At the end of this the phone will reboot for the bootloop but when it boots will show signal and "emergency calls only" message.
--- If you check in Bsaeband will say the right number and no "unknown"
--- Now thanks to Octopus box and their certs support! Write the new cert
--- Everything OK! Phone working and unlocked!
If you want to push thanks I'm okay I should upload images but i was so scared with the phone so I decide to not move anymore xD
If you want to Donate! even a cent! it's good paypal. com /cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=9MJHWHVJW3S94
Click to expand...
Click to collapse
good day,
may I do copy and paste each of the below commands and press enter in order to do it faster?
dd if=/dev/zero of=/dev/block/mmcblk0p10 press (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p13 press (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p14 press(enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p15 press(enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p16 press(enter line)
one more question.....where can I find in Miami area someone with Z3X or Octoplus, ??????
my phone is still under warranty but if I bring it to AT&T and they will ask me what happened ....what should I say in order to get it fixed not for free but almost....
thanks
thepinkpanter said:
good day,
may I do copy and paste each of the below commands and press enter in order to do it faster?
dd if=/dev/zero of=/dev/block/mmcblk0p10 press (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p13 press (enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p14 press(enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p15 press(enter line)
dd if=/dev/zero of=/dev/block/mmcblk0p16 press(enter line)
one more question.....where can I find in Miami area someone with Z3X or Octoplus, ??????
my phone is still under warranty but if I bring it to AT&T and they will ask me what happened ....what should I say in order to get it fixed not for free but almost....
thanks
Click to expand...
Click to collapse
Hi! Here in México. I did try to bring the phone to a samsung support for warranty. They told me that this fix is in warranty police but well I'm in México so they couldn't bring me warranty service. You shouldn't do this method and with the bootloop issue go for your new phone :good: They take this issue as Baseband chip error and replace the board!
i have this problem but in 5.1 any suggerence
frankerebus said:
i have this problem but in 5.1 any suggerence
Click to expand...
Click to collapse
is it possible to repair corrupted baseband and IMEI without downgrading from 5.1.1?
vooks said:
is it possible to repair corrupted baseband and IMEI without downgrading from 5.1.1?
Click to expand...
Click to collapse
Impossible to downgrade from 5.1.1 from what I've read on here.
jack man said:
Impossible to downgrade from 5.1.1 from what I've read on here.
Click to expand...
Click to collapse
Possible to downgrade if you have phone tell me
Faheem anjum said:
Possible to downgrade if you have phone tell me
Click to expand...
Click to collapse
Is it? Downgrading 5.1 to 5.0 or kk is possible? How come :/
Baseband "Unkown" , will this method work on N910S ( SK telecom ) stock 6.0.1, rooted. ?
So it's been a while since I played with ROMs on my v521, but i just upgraded to TWRP 3.1.1-0, and tried to update lineage to the newest nightly. I'm not swuck in a boot-loop.
I've run the commands in terminal that fixed the issue last time I ran into it:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
To no avail - terminal says it can't find the files.
I've wiped everything, reformatted data, reinstalled TWRP, etc.
What's next? How can I break out of the loop?
I fixed it. Grabbed the wrong bookmark. Should have run:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Xerloq said:
I fixed it. Grabbed the wrong bookmark. Should have run:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Click to expand...
Click to collapse
I recently ran into this issue. Thanks for posting the fix!
You saved my butt with this, OP! Thank you!
For those who stumble onto this, the "terminal" he's referring to is the TWRP terminal that is accessible in TWRP>>Advanced>>Terminal.
Thanks for this fix! Could someone please tell me how to type an equal sign (=) in the TWRP terminal keyboard? I can't find it anywhere. I managed to give the tablet these commands with the adb shell.
How to upgrading 3.1.1-0?
How to upgrading 3.1.1-0?
yangseunghwan said:
How to upgrading 3.1.1-0?
Click to expand...
Click to collapse
I am using 3.1.1-0.
Thanks, this worked perfectly! I'm running TWRP-V521-3.0.2.0
How to type an "=" sign in TWRP terminal kb
channeledbymodem said:
Thanks for this fix! Could someone please tell me how to type an equal sign (=) in the TWRP terminal keyboard? I can't find it anywhere. I managed to give the tablet these commands with the adb shell.
Click to expand...
Click to collapse
I'll answer my own question in case someone comes here looking for the answer:
in twrp terminal keyboard to type "=" sign, tap ?123, then ~\{ for special characters including "="
Xerloq said:
I fixed it. Grabbed the wrong bookmark. Should have run:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Click to expand...
Click to collapse
I have been stuck on this issue for over 5 hours thank you so mucn