So while reading the instructions and trying to install the MeDroid ICS 6.1 build... I think I might have bricked my N1. I successfully installed Blackrose. Then watched the video, and repartitioned the system. I then realized that I didn't have the ROM on my microSD card, so I clicked reboot to try to reboot into my CM7 system so I can connect it to my PC and copy over the ZIP of the flash. That's when it all went downhill.
I'm not stuck with the colorful X on my screen. The system doesn't respond to the volume down while I press the power button. If I rerun Blackrose, it crashes, badly. I can't turn off the phone by holding down the power button. I have to pull the battery.
So what do I do now? Need help...
This is by far the worst thing I've done to the phone so far. Everything else has been pretty easy.
Ok, it isn't *completely* dead. I still need some help trying to finish the ICS installation. At this point, I can get back into Blackrose. I guess I wasn't holding down the volume down button properly when I turned it on. So now I can get into Blackrose - Latest version by the way. Now what?
chomerfl said:
Ok, it isn't *completely* dead. I still need some help trying to finish the ICS installation. At this point, I can get back into Blackrose. I guess I wasn't holding down the volume down button properly when I turned it on. So now I can get into Blackrose - Latest version by the way. Now what?
Click to expand...
Click to collapse
Try to download a system.img and boot.img for the ROM you want and flash those from the fastboot mode.
Sent from my Nexus One using Tapatalk
I had the same problem and I figured out that it was happening because of the resized cache partition. If you are using clockwork recovery, that might be your problem. What I did was I flashed Amon's RA recovery by using fastboot. Then I was finally able to boot into recovery. With clockwork, it kept on freezing on the x every time I tried to go into it. After I booted into RA recovery, I wiped cache, data and dalvik cache and then installed ICS from SD. Hope this helps.
I had the same problem too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uh... Yeah, I do run CWM. How do I get into fastboot and install the Amon RA reconvery?
Homer
chomerfl said:
Uh... Yeah, I do run CWM. How do I get into fastboot and install the Amon RA reconvery?
Homer
Click to expand...
Click to collapse
The easy way is to use ROM Manager to flash alternate Amon_RA recovery.
chomerfl said:
Uh... Yeah, I do run CWM. How do I get into fastboot and install the Amon RA reconvery?
Homer
Click to expand...
Click to collapse
Download the RA recovery image onto your computer (should be a .img file). Make sure you have adb and fastboot drivers installed. Turn on your phone while holding volume down and select fastboot from the menu. Connect your phone to your computer via USB. It should say fastboot USB on the screen at this point. Now open command prompt on your computer and navigate to the folder where you have the RA recovery img file. Now type the following into command prompt: fastboot flash recovery filename.img. Replace filename.img with the name of the recovery file. Recovery should now be flashed. Now shut off your phone and restart again while holding volume down. At this point select recovery from the menu and hope that it loads. Worked for me. Make sure you wipe cache, data, and dalvik cache before flashing ICS. Hope this helps.
Sent from my Nexus One
FFVengeance said:
Download the RA recovery image onto your computer (should be a .img file). Make sure you have adb and fastboot drivers installed. Turn on your phone while holding volume down and select fastboot from the menu. Connect your phone to your computer via USB. It should say fastboot USB on the screen at this point. Now open command prompt on your computer and navigate to the folder where you have the RA recovery img file. Now type the following into command prompt: fastboot flash recovery filename.img. Replace filename.img with the name of the recovery file. Recovery should now be flashed. Now shut off your phone and restart again while holding volume down. At this point select recovery from the menu and hope that it loads. Worked for me. Make sure you wipe cache, data, and dalvik cache before flashing ICS. Hope this helps.
Sent from my Nexus One
Click to expand...
Click to collapse
I've following your instructions above, can get to the black/green recovery, and have wiped cache, data, and dalvik cache, but still cant flash any roms.
Flashing CM7.1 gives a E:Can't open /sdcard/rom name.... (bad) error
Flashing MeDroid6.1 will begin installation and go for a few minutes but then shows a 'Random offset: 0x28e' message before the installation finishes. At the end I get a 'Install from sdcard complete' message, but reboot and get stuck at the recovery image.
Flashing MIUI.us_passion_4.0.3-2.2.10_0xD34D gives a E:Can't open /sdcard/rom name.... (bad) error
I've disabled signature verification during all of the above steps
any help would be appreciated...
Is your partition correct?
Sent from my Nexus One
i'm assuming its not.
how do i get back to the default values and what are the default values?
thanks
n1n1n1n1 said:
i'm assuming its not.
how do i get back to the default values and what are the default values?
thanks
Click to expand...
Click to collapse
You should have the stock hboot in your Blackrose folder. You could try to flash it through fastboot by navigating to that folder and using the following commands:
fastboot flash hboot hboot_stock.nb0
fastboot reboot-bootloader
It might not work but it's worth giving it a shot. When I try it on mine it fails but it could be because I have a locked bootloader.
still no luck. i get the following message...
.......directory\Blackrose\hboot>fastboot flash hboot hboot_stock.nb0
sending 'hboot' (512 KB)...
OKAY [ 0.085s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.227s
Related
-------due to the brick phones-------(and im not talking nokia)
I have started this thread to get some clarification on Nandroid back ups. Now i know there is already a thread with step by step instructions in the sticky's. But with all these G1 ones getting bricked due to the new spl incompatibility with the old radio is it safe to use. I ask this only because one of the steps is to have a recovery.img and the only recovery image i can find is for jf1.43 and one other. But none for the adp 1.5 builds. I am worried that if i were to flash a old recovery image, and it down grades my radio i may get bricked. I'm not really sure if that's how it works (if not please correct) and thats why i want to recovery image from the new builds ( i am using Dudes Cupcake 1.1)
Do they exist and if they do and i just haven't search hard enough please tell me. Or is the recovery image what i create when i do the back up. I ask all these perceivable noob questions because i really like my G1 and would hate to brick it.....
Please post some useful Replies... I think this thread could be potentially useful
Doing a nandroid backup creates a boot.img, data.img, and system.img of your phone. Flashing those three, restores your phone exactly as it was when you created the backup. As long as you do a backup of your system when it's stable, then it doesn't matter what you do to your phone. As long as you can get into fastboot, then it can be fixed in less than 5 minutes.
Dunno if that was the answer you were lookin for, but that's how I understand it. And it works....I did a nand backup of my Dude build just yesterday, and flashed over to haykuro's 6.0 to check it out...test drive it. I didn't like it, so I flashed the nandroid backup, and was back up and running in minutes.
You mentioned recovery.img....I don't know what that is or what you do with it.
Assuming you have fastboot setup, just do the steps in this post and you're golden-
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware
ESKIMOn00b said:
the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware
Click to expand...
Click to collapse
Right on, thanks for that. Knowledge is power.
So the op says that he found the JF1.43 recover.img....That's the one we all have and the one he needs, right?
yep, they're all the same
All the recent ROMs EXCEPT for the official HTC ADP use the same recovery.img found in the previous JF ROMs (1.42, etc.). You can safely reflash the recovery image from fastboot without touching the radio, the SPL or even data, boot or system if you want and it won't hurt anything.
remember when you orig rooted your phone and the recovery mode didnt have the fractal background and you had to press alt+l to show the text? thats the OLD recovery img, the fractal bkgrnd (v1.43) one is the new one, and so far the latest "cooked" recovery.img
Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.
Great post. +1
pshadey said:
Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.
Click to expand...
Click to collapse
correct...
the fastboot.exe is how your PC will interface with the FASTBOOT mode in the SPL
if you didnt have it DL'ed when you tried to fastboot, your computer would kickback that fastboot isnt a valid command or the like (depending on os)
so im reading all these tutorials, and im getting confused a little... to use fast boot through adb does my phone need to be at the boot loader (skateDroids) or are there commands that i would need to enter in order to get there....
I appriciate every answer i am trying to learn as much as i can. This has really spark a interest in my life and i really enjoy it.
fastboot is not part of adb, and yes your phone needs to be in bootloader to FASTBOOT, after entering bootloader plug in the usb cable and press the back button, your phone should read FASTBOOT rather than serial0
adb works almost anywhere (after splash1/g1 logo) except bootloader...
for reference ADB stands for Android Debug Bridge
I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b
pshadey said:
I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b
Click to expand...
Click to collapse
Yep. Boot your phone with home+power, then Alt+B. It'll create a folder on your sdcard called nandroid. All the .img files will be in there.
i dont think i have the right recovery image though do i just download the zip file. and do the whole rename to update.zip and install alt-s.
I only ask because i opened the file and found a recovery.img which made me ponder.
thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...
~edit~
I see I misunderstood the question. Duh
ESKIMOn00b said:
thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...
Click to expand...
Click to collapse
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????
This is what your recovery mode will look like after you update it-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't answer your question about how to update to it though. Mine's been this way since waaay back when I flashed JF's RC33.
yea, thanks bro. mine definitely does not look like that. but now i need to know for sure how to update it.
pshadey said:
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????
Click to expand...
Click to collapse
I am having the same problem... I am on the Dude's Cupcake 1.1a but I dont see ant Alt-B option...
Android system recovery utility
E:Can't open /cache/recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
Click to expand...
Click to collapse
Thats all i have on my screen.
As it says above THIS is why i cant boot up hero roms or any other that doesnt use cupcake/donut boot does ANYBODY have ANY IDEAS!!??!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also tried using adb shell to flash the boot but get error writing on block xxxxxxxxxx
I used RA_dream-v1.2.2 today threw ADB. Placed .img on root of sd,
Dont use mount -a, mount /system, or mount /sdcard
Just use
# mount
# flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img
http://forum.xda-developers.com/showthread.php?t=566669
Its the boot img that wpnt flash not the recovery but thanks anyhow
bumping this thread as i am pretty stuck.Not being able to write the boot.img means even my nandroid wont work
can you get a different boot.img to try it might be curupt
found this
http://forum.xda-developers.com/showthread.php?t=509248
use adb shell
also i see you deleted recovery installed new recovery removed system then you tried to install boot
did you try to install system first before both recovery and boot
i'm no expert lol
found some other stuff
How to restore from your backup file
1. Download one of the above signed SPL updates and rename it to update.zip
2. Copy update.zip to the root of your SD-card
3. Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder C:\Android.
4. booting your Magic into recovery model
5. select [Alt + S] – Apply sdcard:update.zip
6. select [Home + Back] – reboot system now
7. After reboot it will update upgrade/downgrade your SPL version, then power off your Magic again
8. Push “Back” + “Power” to HBOOT model
9. double check your SPL version is upgrate/downgrate
10. Plug the USB cord back into your phone. The screen on your phone should say fastboot.
12. Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
13. Type cd C:\android
11. then enter the following commands C:\android >
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
12. After reboot your Magic, it need about 2-5 min to restore
13. then a band new original Android 1.5 is restored
Yes i have tried that, The problem is the boot.img. I cant flash it! Nandroid restore fails due to boot.img (cannot be flushed!) Thanks for the speed yresponse but still no joy
bonesy said:
Yes i have tried that, The problem is the boot.img. I cant flash it! Nandroid restore fails due to boot.img (cannot be flushed!) Thanks for the speed yresponse but still no joy
Click to expand...
Click to collapse
Did you follow ALL steps while rooting your 32B?
I'm almost 100% sure that you are using your 32B with a 32A radio and rom, right? Complete the rooting by following the "Revert to 32B Radio and ROM" exactly to the letter in this thread. Do not try to do something else or you'll brick it.
i followed all steps apart from using the gold card as i couldnt make one and reverted back to 32B using your steps. I also did it all again but using flashrec.apk?
try this flashrec.
worked for my 32A
http://zenthought.org/content/project/flashrec
Done the flashrec thing, Quite a few times now i have a feeling as it was repaired by htc and sent back they have made it so the boot.img cannot be written in any way, If i use a friends nandbackup of hero it fails (not that it says so) and just keeps on the splash screen untill the phone becomes so hot it switches off! Giving up on this, Gone back to standard (rooted) rom and will await the sense update (fingers crossed)
Stil lthe same problem...although it WILL let me flash sapphire boot just not a modified boot see here....
First flashed boot.img is the google ion boot off of the htc site
Second is the tattoo boot.img modified for the sapphire. Any ideas?
Anyone know where i can get the Google Ion hboot from? just wanna try one more thing before i give up!
Have you posted this in Dream Q&A? That forum is way more active and there is alot more knowlege on things like this. Maybe send David1077 a PM. I feel bad because I have looked at your post for quite a few weeks now with little help. Good luck
i would but am afraid of a ban for posting in wrong forums,ive already done that lots!
somprogress
seems lile i can fastboot boot the img but it just loops at the boot screen?as i say donut roms work fine but ANY sense ui fail at line 92
Right im now offering £25 if anyone can get sense ui working on my phone.any info they need i will give!
bonesy said:
Stil lthe same problem...although it WILL let me flash sapphire boot just not a modified boot see here....
First flashed boot.img is the google ion boot off of the htc site
Second is the tattoo boot.img modified for the sapphire. Any ideas?
Anyone know where i can get the Google Ion hboot from? just wanna try one more thing before i give up!
Click to expand...
Click to collapse
http://www.4shared.com/file/143324302/e942c9d8/boot.html
not to sure what your asking for but this is a boot.img from my signed-google_ion-img-14721
have you looked here iknow you would of but just in-case
http://developer.htc.com/google-io-device.html
my original boot.img
http://www.4shared.com/file/143325952/211edf2e/_2__boot.html
this one is from inside the MLIGN-MagicV1.0-FINAL rom
http://www.4shared.com/file/143326459/aca13a1b/_3__boot.html
the problem is i cant write the boot img in any way.Only original boot.img files not any that are modified.
Its the HBOOT i need to try, But thanks
bonesy said:
the problem is i cant write the boot img in any way.Only original boot.img files not any that are modified.
Its the HBOOT i need to try, But thanks
Click to expand...
Click to collapse
so what is the hboot?
what are you excactly asking for
The hboot is the spl, im asking for the dev one as its naturally enabled for fastboot therefore im trying to trick my phone to make it think its the dev phone (Google ion) hopefully bypassing the "REMOTE: image update error'' when writing boot.img
have you tried the one i'm on Engineering SPL 1.33.2004 by Crios
Engineering SPL 1.33.2004 by Crios is actually a hex-edit of SPL 1.33.2005 to fool updates.
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
stargirl29 said:
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
Click to expand...
Click to collapse
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
fastboot
Evolution_Tech said:
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
Click to expand...
Click to collapse
i'm not really sure how to do that.
stargirl29 said:
i'm not really sure how to do that.
Click to expand...
Click to collapse
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
fastboot
Evolution_Tech said:
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
stargirl29 said:
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
Click to expand...
Click to collapse
Factory reset from recovery.
Evolution_Tech said:
Factory reset from recovery.
Click to expand...
Click to collapse
if you mean this, https://support.google.com/nexus/answer/4596836?hl=en
yes. that was the first thing i did. and always the first thing i try before using any toolkits or manual repairs.
i ran Wugs again today and FINALLY got it back to the sign in screen to setup the tablet. everything was going great. then i got back into the bootloader to lock the oem. and when it restarted i'm still getting the "optimizing apps x of 99" which is annoying but it seems my tablet is at least usable for now.
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
fixed it!
vipthomps said:
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
Click to expand...
Click to collapse
i fixed it with Wugs yesterday, finally! after 5 days of trying.
okay hello people.
here is my situation.
i was about to revert back to kitkat from ED300 CM12.1, and i suddenly wipe off and formatted my internal storage.
and now ofcourse i cant boot in and what i did was trying to reinstall TWRP through fastboot and minimal adb from PC.
*i tried to flash Lenovo_A6000_TWRP-3.0.2-0_x64-L_by_SevenMaxs
*i cant go into download mode (vol+,vol-,power) button.
so i went to fastboot mode (vol-,power) button until the 'powerkey long press can reboot phone' appear , and i plug in my phone to pc and when i type in command for -adb devices, no device appear.
figure out it was okay, i go ahead and proceed with - fastboot boot recovery.img command.
then it shows
FAILED (remote: dtb not found)
and im stuck there. idk what else to do, which guide to follow to bring my phone back to life.
i have did hours of searching but nothing works. really need a magic here.
thanks guys for ur time
rizarulaltiz said:
okay hello people.
here is my situation.
i was about to revert back to kitkat from ED300 CM12.1, and i suddenly wipe off and formatted my internal storage.
and now ofcourse i cant boot in and what i did was trying to reinstall TWRP through fastboot and minimal adb from PC.
*i tried to flash Lenovo_A6000_TWRP-3.0.2-0_x64-L_by_SevenMaxs
*i cant go into download mode (vol+,vol-,power) button.
so i went to fastboot mode (vol-,power) button until the 'powerkey long press can reboot phone' appear , and i plug in my phone to pc and when i type in command for -adb devices, no device appear.
figure out it was okay, i go ahead and proceed with - fastboot boot recovery.img command.
then it shows
FAILED (remote: dtb not found)
and im stuck there. idk what else to do, which guide to follow to bring my phone back to life.
i have did hours of searching but nothing works. really need a magic here.
thanks guys for ur time
Click to expand...
Click to collapse
BTW if "fastboot devices" not showing any devices then try to properly install fastboot on computer."fastboot boot twrp.img" is command for boot the twrp without flashing.
try "fastboot flash recovery twrp.img" .
p.s:-Try to flash different recovery file.It may be corrupted.
i-AM-BoReD said:
BTW if "fastboot devices" not showing any devices then try to properly install fastboot on computer."fastboot boot twrp.img" is command for boot the twrp without flashing.
try "fastboot flash recovery twrp.img" .
p.s:-Try to flash different recovery file.It may be corrupted.
Click to expand...
Click to collapse
did it as your advice,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then i reboot the phone, still cant manage to go into recovey. it stuck there at lenovo logo.
tried with different recovery image, still the same
rizarulaltiz said:
did it as your advice,
then i reboot the phone, still cant manage to go into recovey. it stuck there at lenovo logo.
tried with different recovery image, still the same
Click to expand...
Click to collapse
As i can see that it is saying device not found but flshing is succeeded.
Editlz try to install fastboot properly.Look here
i-AM-BoReD said:
As i can see that flashing is successful.For entering to recovery r u using button combo or command?
Click to expand...
Click to collapse
i use button combo.
vol+, vol-, power button
rizarulaltiz said:
i use button combo.
vol+, vol-, power button
Click to expand...
Click to collapse
Here is the possibilities:-
1)May be fastboot is not properly installed .I gave a link in the previous post for that. "device not found" that shouldn't be appear.
2)Try vol+ +power button
3)Try if stock recovery can be flashed by fastboot.Link.if can be then let me know.
4)If not then run this command in adb
Code:
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
and give a screen shot.
Did you flash kitkat ROM after this or before this fuss?
If Yes, then you need to flash TWRP for kitkat firmware.
https://drive.google.com/file/d/0B8_p5nNeW71VRFZnc3cwb2hLR28/view?usp=sharing
download the above recovery and download flashify from playstore . Flash the recovery that you downloaded from above link with flashify and reboot and in the next step you will be in the recovery
Try this
http://forum.xda-developers.com/len...lenovo-a6000-plus-stuck-booting-logo-t3437378
LP/MM TWRP 2.8.7.7 https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
KK TWRP 2.8.6.1 https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk
i-AM-BoReD said:
Here is the possibilities:-
1)May be fastboot is not properly installed .I gave a link in the previous post for that. "device not found" that shouldn't be appear.
2)Try vol+ +power button
3)Try if stock recovery can be flashed by fastboot.Link.if can be then let me know.
4)If not then run this command in adb
Code:
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
and give a screen shot.
Click to expand...
Click to collapse
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?
rizarulaltiz said:
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?
Click to expand...
Click to collapse
Then ur device is good to go.I found a recovery flashble stock rom in help or guide thread few days ago.Search it.
Also if there is recovey flashable T.W.R.P available somewhere u can flash it also.
Edit:-Here is a zip file of T.W.R.P.But version is 3.0.0.1.Don know if it can be flaahed by Stock recovery or not.Give it a try.If succeeded then no need to flash whole stock rom.You know that already.
i-AM-BoReD said:
Then ur device is good to go.I found a recovery flashble stock rom in help or guide thread few days ago.Search it.
Also if there is recovey flashable T.W.R.P available somewhere u can flash it also.
Edit:-Here is a zip file of T.W.R.P.But version is 3.0.0.1.Don know if it can be flaahed by Stock recovery or not.Give it a try.If succeeded then no need to flash whole stock rom.You know that already.
Click to expand...
Click to collapse
after i manage to flash stock recovery, i flash TWRP-2.8.6.1_A6000. then i boot into TWRP and format my internal storage, then continue flashing back ED 300's CM12.1.
and my device is back onlinee! Thanks brother for the help!!!
rizarulaltiz said:
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?
Click to expand...
Click to collapse
I am facing the same problem of adb device not listed , please share how it worked for you
Hi,
I was trying to install Super Rom but unfortunately I am unable to boot the phone. I had rooted the phone a while back. When I try to turn the phone on I get stuck with the dreaded static screen which is normally an easy fix however I can't boot into TWRP as that gives my a static screen too. The only thing I have access to is the fastboot menu and when I try "fastboot reboot" I get stuck at the LG "lifes good" screen. I have tried to flash two different versions of TWRP (one given in dirty santa and the most up to date for H990DS).
Any ideas will be greatly appreciated!
SOLUTION: https://forum.xda-developers.com/showpost.php?p=77843686&postcount=7
Don't use fastboot reboot. That starts it booting the stock rom, which before the first boot into twrp reflashes the stock recovery again. You need to pull the battery to leave fastboot, then boot into recovery by holding volume down, holding power until the screen turns on, then tapping power repeatedly until it asks to factory reset, say yes. When twrp boots swipe to allow writing to system and flash something. Then booting the rom won't eat twrp anymore.
Phoenix591 said:
Don't use fastboot reboot. That starts it booting the stock rom, which before the first boot into twrp reflashes the stock recovery again. You need to pull the battery to leave fastboot, then boot into recovery by holding volume down, holding power until the screen turns on, then tapping power repeatedly until it asks to factory reset, say yes. When twrp boots swipe to allow writing to system and flash something. Then booting the rom won't eat twrp anymore.
Click to expand...
Click to collapse
Thanks for your help, but I have managed to fix my issues! I will add in a fix guide later for anyone else that stumbles upon this.
Phoenix591 said:
Don't use fastboot reboot. That starts it booting the stock rom, which before the first boot into twrp reflashes the stock recovery again. You need to pull the battery to leave fastboot, then boot into recovery by holding volume down, holding power until the screen turns on, then tapping power repeatedly until it asks to factory reset, say yes. When twrp boots swipe to allow writing to system and flash something. Then booting the rom won't eat twrp anymore.
Click to expand...
Click to collapse
So I can now boot into SuperRom but I am unable to go back into TWRP. When I do the usual button procedure to get to TWRP I am asked to do the LG reset thing, I press yes twice and then I am met with this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To boot into Android I need to open fastboot and reflash the recovery, then reboot but I still don't have any access to the recovery. Any ideas?
Higgings said:
So I can now boot into SuperRom but I am unable to go back into TWRP. When I do the usual button procedure to get to TWRP I am asked to do the LG reset thing, I press yes twice and then I am met with this screen:
To boot into Android I need to open fastboot and reflash the recovery, then reboot but I still don't have any access to the recovery. Any ideas?
Click to expand...
Click to collapse
Flash my twrp instead.
Phoenix591 said:
Flash my twrp instead.
Click to expand...
Click to collapse
I'm fairly certain that's the one I'm using, but ill re-download it and try again.
Just downloaded your version and it was indeed the one I have been using already. I did however download it again and tried to reflash it using the method you stated above but I end up with the same screen. The only way I can get it to boot into Android after that screen is to boot into fastboot, flash your recovery then "fastboot reboot".
Problem solved! Solution:
1. Download the TWRP app from the play store
2. Using the app, flash Phoenix591's TWRP (here)
3. Use ADB and reboot into recovery using "adb reboot recovery"
Once I did these steps I was able to use the usual method (volume down, release power for one second etc) to boot into TWRP. Happy days!