Hi,
i think My A100 is completly bricked ..The Story:
my Tab was rooted and Unlocked TWRP was installed and running FlexReaper Rom.
1.i decided to reset my A100 completly to stock -> downloaded 014 ICS Rom and Named it update.zip
2. i want to flash this trough recovery when it searches for update.zip files but its not working (dont finding this file)
3. i flashed it in TWRP Recovery after it was done it says no OS installed but i ignored it (*facepalm*) <---I KNOW THIS WAS STUPID !
now the Tablet dont boot Android (stuck at white Acer Logo )and when trying to start revovery its says in Red Letters: Recovery verified failed ...
Bootloader is LOCKED and NOT Rooted
im able to get in Fastboot Mode but the Tablet accept only a very small amount of commads from adb.
my Question : is this Tablet ready to get back to Acer ?
i've tryed unlocking the BootLoader using the Fastboot oem unlock cmd to install the Recovery.img ,but nothing happend only the Screen blanks out for half a second.
and i tryed flash an update.zip from External SDCard but this doens't work as before the Brick.
Anyone have an Idea ? i hope you understand my English and my Problem, i'm from Germany.
Benny164 said:
Hi,
i think My A100 is completly bricked ..The Story:
my Tab was rooted and Unlocked TWRP was installed and running FlexReaper Rom.
1.i decided to reset my A100 completly to stock -> downloaded 014 ICS Rom and Named it update.zip
2. i want to flash this trough recovery when it searches for update.zip files but its not working (dont finding this file)
3. i flashed it in TWRP Recovery after it was done it says no OS installed but i ignored it (*facepalm*) <---I KNOW THIS WAS STUPID !
now the Tablet dont boot Android (stuck at white Acer Logo )and when trying to start revovery its says in Red Letters: Recovery verified failed ...
Bootloader is LOCKED and NOT Rooted
im able to get in Fastboot Mode but the Tablet accept only a very small amount of commads from adb.
my Question : is this Tablet ready to get back to Acer ?
i've tryed unlocking the BootLoader using the Fastboot oem unlock cmd to install the Recovery.img ,but nothing happend only the Screen blanks out for half a second.
and i tryed flash an update.zip from External SDCard but this doens't work as before the Brick.
Anyone have an Idea ? i hope you understand my English and my Problem, i'm from Germany.
Click to expand...
Click to collapse
Its not bricked, its working as intended. You did however lock yourself out. Keep doing the update.zip method, its the only way.
Tapatalked from my Galaxy S II.
I have tried the update.ZIP method with my Sandisk 8GB MicroSD but its not Working ... do you have a update.ZIP for me ?
Galaxy Nexus - Tapatalk
Benny164 said:
I have tried the update.ZIP method with my Sandisk 8GB MicroSD but its not Working ... do you have a update.ZIP for me ?
Galaxy Nexus - Tapatalk
Click to expand...
Click to collapse
It may not even work without at least the stock recovery there, but I would try the 014 in vaches thread with the stock ROMs. One was decrypted and is on a drop box I think, use that one. Triple check you name it update.zip all lower case and turn off hide file extensions to check it only has 1 .zip there.
Sending it to Acer may be your only choice now.
Tapatalked from my Galaxy S II.
Ok ...do you think i musst pay acer or only shipping ?
Galaxy Nexus - Tapatalk
Benny164 said:
Ok ...do you think i musst pay acer or only shipping ?
Galaxy Nexus - Tapatalk
Click to expand...
Click to collapse
You'll have to pay, its user error not a hardware failure. Unless you get really lucky, half the bricks are charged for repairs because it happens on a custom rom and that IS hardware failure.
Custom ROM + Custom recovery = warranty gone
Tapatalked from my Galaxy S II.
at the Moment i have completly Stock Firmware ...i think update.zip wont work tried a couple of Times no Luck.
I have attached a Picture.
I'd have to say with a borked recovery and a locked bootloader, you really can't do anything. You need at least one of them to even attempt anything besides the stock update.zip.
Thanks for your post. I'm running the exact same way. And was wondering how to go completely stock again, if need be. I think maybe flashing back to the stock recovery with zn's script, then applying the .014 stock package. I'm not brave enough to try though. I'm pretty sure a stock update will flash over an unlocked boot loader and root, no problem, but the recovery is the issue. Which your problem seems to reflect.
Yes i think im going to send it to Acer Repair Center
Galaxy Nexus - Tapatalk
You could flash the stock bootloader/recovery through adb,
Like
Fastboot flash recovery.img
Or something,
If your in tested I could look into it.
sent from my A1/500 Iconia slab of awsomeness
Do you have a link for the 014 ics recovery.IMG ?
Galaxy Nexus - Tapatalk
http://forum.xda-developers.com/showthread.php?t=1730093
Since your bootloader is locked I highly doubt it will push any files. But it never hurts to try.
das_webos_transformer said:
You could flash the stock bootloader/recovery through adb,
Like
Fastboot flash recovery.img
Or something,
If your in tested I could look into it.
sent from my A1/500 Iconia slab of awsomeness
Click to expand...
Click to collapse
That would work except two things.
1 stock a100 boot loader has no fastboot access or adb.
2 custom recovery has abd but is locked out by a100 boot loader.
Its stuck, no matter what.
The proper method to restore is simple, but tends to fail, and that's letting it run update.zip on its own.
Stock update will:
Erase cache, format system and data
Install system
Install boot loader
once booted it will flash stock recovery.
Safest method to return to stock:
Edit the stock ROM, remove bootloadr.blob from zip and updater script.
Save and re zip
Flash the stock system
Boot stock system
Root stock system
At this point you will have stock system, but a200 boot loader.
Reboot and check recovery for stock with adb reboot recovery
If its stock recovery you can then use the revert a100 bootloader script to flash back to locked a100.
Its long and annoying, but its the only way to verify each step without getting locked out.
Since he forced it in custom recovery it failed to install system but did install the bootloader, so they got stuck with a locked bootloader that cant be unlocked and a custom ROM and recovery, so locked out.
You could try a hard reset, it might kick start the stock ROM into working with the bootloader...
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
pio_masaki said:
That would work except two things.
1 stock a100 boot loader has no fastboot access or adb.
2 custom recovery has abd but is locked out by a100 boot loader.
Its stuck, no matter what.
The proper method to restore is simple, but tends to fail, and that's letting it run update.zip on its own.
Stock update will:
Erase cache, format system and data
Install system
Install boot loader
once booted it will flash stock recovery.
Safest method to return to stock:
Edit the stock ROM, remove bootloadr.blob from zip and updater script.
Save and re zip
Flash the stock system
Boot stock system
Root stock system
At this point you will have stock system, but a200 boot loader.
Reboot and check recovery for stock with adb reboot recovery
If its stock recovery you can then use the revert a100 bootloader script to flash back to locked a100.
Its long and annoying, but its the only way to verify each step without getting locked out.
Since he forced it in custom recovery it failed to install system but did install the bootloader, so they got stuck with a locked bootloader that cant be unlocked and a custom ROM and recovery, so locked out.
You could try a hard reset, it might kick start the stock ROM into working with the bootloader...
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
Click to expand...
Click to collapse
how i do a Hard Reset ?
when i try flashing the recovery.img its says : unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
Benny164 said:
how i do a Hard Reset ?
when i try flashing the recovery.img its says : unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
Click to expand...
Click to collapse
Its the one where you power on holding volume + then toggle the lock switch a few times.
fastboot flash recovery recovery.img
Must have recovery where fast boot is run from.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
pio_masaki said:
Its the one where you power on holding volume + then toggle the lock switch a few times.
fastboot flash recovery recovery.img
Must have recovery where fast boot is run from.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
Click to expand...
Click to collapse
hard reset works but adb fails : C:\Users\Benny>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
Benny164 said:
hard reset works but adb fails : C:\Users\Benny>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
Click to expand...
Click to collapse
Well for one, recovery.img must be in the same folder, and that files name used in the command.
Second, fast boot doesn't work on a100 bootloader as I already mentioned.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
pio_masaki said:
Well for one, recovery.img must be in the same folder, and that files name used in the command.
Second, fast boot doesn't work on a100 bootloader as I already mentioned.
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
Click to expand...
Click to collapse
oh ok ... so do you guys have another Idea ?
Benny164 said:
oh ok ... so do you guys have another Idea ?
Click to expand...
Click to collapse
Does adb work? Not fast boot but adb. Try adb devices
Tapatalked from my Kindle Fire - Hellfire Jelly CM10
No in Fastboot Mode no devices have been Detected in Adb. I think my Android SDK Installation is OK ..my Windows 7 PC Sees my Galaxy Nexus in Toolkit.
Galaxy Nexus - Tapatalk
Related
Hi, i just got my Galaxy Nexus and unlocked+rooted it with the Toolkit v6.1.
Then i flashed CWM Recovery and tried flashing a Rom (Slim ICS), but i got the error: E: Can't open /sdcard/Base_3.6.zip (bad) Installation aborted.
What is also unnormal: I can't boot into Recovery normally. When i try to get into recovery via Fastboot, i get Screen with a green Android, laying down, chest open, with a red sign in it. Well, doesnt look so good...
I was only able to recovery when i flashed it via Rom Manager and then booted to it via Rom Manager. Whats also strange: After Wiping & trying to flash (back @ stock settings), the recovery seemed to be gone again. I had to reflash it again via Rom Manager, to make it work.
I got the impression, that there is something wrong with my phone's permissions. Any ideas how i can fix that?
Thx for the help!
W4yl4nder said:
..I was only able to recovery when i flashed it via Rom Manager and then booted to it via Rom Manager..
Click to expand...
Click to collapse
thats the problem, flash the recovery via fastboot. rom manager really sucks, im surprised so many people use it. in the end, it causes more headaches than it prevents. btw, you should try twrp recovery instead, its much better than cwm recovery.
Please don't use toolkits or all-in-one's or one-click's unless you understand what they do and how they do it. There's simply no need for a toolkit on this device.
Code:
> fastboot oem unlock
> fastboot flash clockworkmod-recovery.img recovery
Then you know that it's done, and done properly. I bet if you do that, you'll then be able to boot directly into recovery.
codesplice said:
Please don't use toolkits or all-in-one's or one-click's unless you understand what they do and how they do it. There's simply no need for a toolkit on this device.
Code:
> fastboot oem unlock
> fastboot flash clockworkmod-recovery.img recovery
Then you know that it's done, and done properly. I bet if you do that, you'll then be able to boot directly into recovery.
Click to expand...
Click to collapse
actually, it's 'fastboot flash recovery clockworkmod-recovery.img'.
Sent from my Transformer Prime TF201
bk201doesntexist said:
actually, it's 'fastboot flash recovery clockworkmod-recovery.img'.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
That too, sorry. Got my head twisted up trying to handle [ CODE ] tags from my phone.
i got the recovery now (forgot to delete auto-reflash-recovery-on-boot file :/), but its still not working. when trying to flash a rom i still get the same error (also in twrp recovery).
W4yl4nder said:
i got the recovery now (forgot to delete auto-reflash-recovery-on-boot file :/), but its still not working. when trying to flash a rom i still get the same error (also in twrp recovery).
Click to expand...
Click to collapse
Verify that the zip is good?
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
jhonnyx said:
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
Click to expand...
Click to collapse
You can flash a custom recovery like cwm or twrp. Then you can acces the custom recovery and adb push your ROM and gapps. Then you do the wipes and flash the ROM and gapps. If you dont understand anything you just have to tell me
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks mrgnex. I've tried flashing TWRP, but the only thing it does is boot into stock recovery and tries to flash a file from /cache/, which file is: 5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip; pretty weird. Issue is the same as this thread: http://forum.xda-developers.com/showthread.php?t=1909331&page=4
use: fastboot boot recovery.img
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
doesnt matter. whichever.
jhonnyx said:
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
Click to expand...
Click to collapse
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
TheMysteriousOne said:
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
Click to expand...
Click to collapse
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
jhonnyx said:
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you elaborate on why exactly you were not able to install TWRP?
TheMysteriousOne said:
Can you elaborate on why exactly you were not able to install TWRP?
Click to expand...
Click to collapse
Surely:
1 - Unlock via fastboot oem unlock
2 - fastboot erase recovery (exits with ok)
3 - fastboot flash recovery twrp_versiondoesnotmatter.img (exits with ok)
4 - reboot w/power+vlup+voldown and select reboot recovery
5 - stock recovery appears
an alternate method that i've tried:
1 - Unlock via fastboot oem unlock
2 - fastboot boot twrp_versiondoesnotmatter.img (exits with ok)
3 - TWRP boots and flashes a zipfile from /cache/ then reboots automatically
That's what happens. A mistery, huh?
Also I've tried OMAP Flash, and; the same issue happens over and over again
Have you tried doing a factory reset using the stock recovery?
TheMysteriousOne said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
AFAIK, Yes
What happens once I start the stock recovery; as I've already stated; starts flashing a zip file located into /cache/ (5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip); then bleh, starts the bootloop again.
I've tried the power+volup then selected wipe cache and wipe system and it's the same.
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
$Parker said:
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
fastboot flash boot <path to twrp>.img does not boot the recovery . I mean; still boots the normal Kernel.
Actually I'm trying what TheMysteriousOne told me by downloading the stock Gnex zip (250Mb) to flash via Odin.
Ohh, bad luck strikes again:
<ID:0/011> system.img
<ID:0/011> Complete(Write) operation failed.
cannot write system.img :/
Any ideas?
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
Pardon me, if EMMC/Board is dead; why does it boot or get into bootloop? There is something that reflashes itself; it even overrides odin or heimdall...
Have you tried going back to completely stock using the method outlined here? http://forum.xda-developers.com/showthread.php?t=1626895
jhonnyx said:
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/showthread.php?t=2016628
a manta wrote this.
I tried to root my N7 (2013) today and i ended up with a black screen.
I used these instructions, but got a bootloop on the Nexus Logo.
http://forum.xda-developers.com/showthread.php?t=2382051
So i tried to do a factory reset via TWRP, without luck (errors in twrp)
I couldn't even mount to get an ROM on the device.
Then i tried to do a factory restore with the *.img files from:
http://forum.xda-developers.com/showthread.php?t=2381582
Still no boot (only nexus logo).
So i tried to do a factory reset via the stock recovery.
After this all i got is an black screen.
First i thougt it was hardbricked. But i recognized that the device manager from windows 7 shows the device.
could not get adb to work while it shows "Android ADB Interface"
But if i turn it off and boot with volume down pressed i can get into bootloader ("android bootloader interface" at device manager)
And then i can connect via fastboot. but still nothing on the screen...
Is there more to restore than recovery/system/boot ? any display driver or kernel, so that the screen will start working again?
Otherwise i will go to the store and get me a new one.
Have you tried to reflash twrp? Or flash cwm instead? Mine didn't want to take twrp but flashed cwm without issues.
Sent from my SCH-I535 using Tapatalk 4
If you can get into bootloader (ie. fastboot sees the device), you should be able to at least throw the stock image back on there by running the included flash-all script provided by Google.
You should be able to replace the recovery as well. TWRP2 works nicely for me. Maybe download your copy again (http://techerrata.com/browse/twrp2/flo) and check the md5 has to make sure your download is good. Then flash with "fastboot flash recovery <*.img>". From there you can then install whatever you want.
As long as you can get into the bootloader, your options are many.
i just tried the flash-all script provided by google.
But still just a black screen...
I could flash a custom recovery, but i think this would not help the display problem.
if no one else have an idea for a solution i will lock the bootloader and bring it to the store tomorrow.
edit: got a new one. already rooted and with working twrp.
Whenever I turn on my Htc one vx it goes to the htc boot logo and under it it has the words in red letterss. "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply May lead to legal Action." I tried to root it but had some trouble and when i get into boot loader it says at the top tampered and unlocked. Any help is greatly appreciated.
zeroelement said:
Whenever I turn on my Htc one vx it goes to the htc boot logo and under it it has the words in red letterss. "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply May lead to legal Action." I tried to root it but had some trouble and when i get into boot loader it says at the top tampered and unlocked. Any help is greatly appreciated.
Click to expand...
Click to collapse
explain all steps you did already and also if you where on 4.0 or 4.1.2 i will try to help if i can.
Sorry for the late response. I don't remember too well. I watch a guide with the normal commands to root it but was stuck where it was rooted but i could not load super user. I made the mistake of trying to unroot it and then it got stuck at the screen. I think I don't have the stock rom loaded on the phone anymore but I am not sure and I don't know how to load a rom but I can easily learn. Thank you for your help
Do you have a custom recovery on the phone
Sent from my HTC One VX using xda app-developers app
I don't believe so.
zeroelement said:
I don't believe so.
Click to expand...
Click to collapse
ok well if you are still unlocked fastboot flash a recovery then flash a stock rooted rom i would try ICS frist because if you have not flashed a JB RUU or the JB firmware you should still be on ICS 4.0 firmware unless you know you where on JB 4.1.2 if so install the JB stock rooted rom. to do that after you fastboot flash the recovery and have DL the rom just put the rom on a ext. SD card via PC sd card reader. also extract the boot.img from the rom and put it in the same dir. that you have adb and fastboot files. boot into recovery.Do a factory reset wipe from the recovery then install the rom for SD card. After it installs reboot to bootloader fastboot then fastboot flash the boot.img . Hint wherever you have adb fastboot files just open that dir and hold shift and right click and that will give you the option to open cmd propt in that dir. then do your fastboot flash cmd. that should do it and get you up and running again. hope it helps
kalel420 said:
ok well if you are still unlocked fastboot flash a recovery then flash a stock rooted rom i would try ICS frist because if you have not flashed a JB RUU or the JB firmware you should still be on ICS 4.0 firmware unless you know you where on JB 4.1.2 if so install the JB stock rooted rom. to do that after you fastboot flash the recovery and have DL the rom just put the rom on a ext. SD card via PC sd card reader. also extract the boot.img from the rom and put it in the same dir. that you have adb and fastboot files. boot into recovery.Do a factory reset wipe from the recovery then install the rom for SD card. After it installs reboot to bootloader fastboot then fastboot flash the boot.img . Hint wherever you have adb fastboot files just open that dir and hold shift and right click and that will give you the option to open cmd propt in that dir. then do your fastboot flash cmd. that should do it and get you up and running again. hope it helps
Click to expand...
Click to collapse
Okay thanks I will try that and get back to you
When I got to flash a recovery I type "fastboot flash recovery twrprecovery.img" while my phone is plugged in while in bootloader but it just says waiting for device. I dont have any drivers installed and I think that is the problem. How can I install drivers without htc sync because The device doesn't show up? Thanks
Nevermind I found the htc drivers.
THANK YOU SO MUCH IT WORKED!!! My phone has been like this for months! You are a lifesaver! I don't need to send it in to be fixed for money! Thank You so much you are the best!
zeroelement said:
THANK YOU SO MUCH IT WORKED!!! My phone has been like this for months! You are a lifesaver! I don't need to send it in to be fixed for money! Thank You so much you are the best!
Click to expand...
Click to collapse
No problem glad i could help.
I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs