my rooted stock ics (not cm) thinkpad decided to stuck in the boot screen (lenovo sign) and i wonder if i can do anything to save data (from internal sd, but also all app data i would be happy to have). perhaps cwm can be installed still in some way so i can make a (nandroid) backup of my data, i have many stuff on it and i'm a bit panicked that i will lose everything. i tried to wipe cache but that freezes at the 'deleting..' stage. also i tried adb when in the recovery, but that does not work.
is there any way to install cwm without data wipe? e.g. in the recovery menu there is an option to update from external sd where i can choose the img file, if i choose your cwm recovery.img would it install the cwm or rather brick the device?
as another possibility i just read something about nvflash. can i save my data using that?
please help,
thanks
mnb
if your bootloader is unlocked then you can use nvflash to backup all you partitions, including internal sd.
berbecverde said:
if your bootloader is unlocked then you can use nvflash to backup all you partitions, including internal sd.
Click to expand...
Click to collapse
thanks,
i tried nvflash but it gives this error:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
so i assume my bootloader is locked? is there still a chance with nvflash. or any other trick? (e.g. updating to the cwm recovery.img i asked about) i use win7 x64 btw, can that cause an issue with nvflash?
Yes it means it is locked. So you can not use nvflash.
I do not know if you can use ADB. You can try to see if you can install CWM.
berbecverde said:
Yes it means it is locked. So you can not use nvflash.
I do not know if you can use ADB. You can try to see if you can install CWM.
Click to expand...
Click to collapse
no, i cannot get to a state when adb works.
i was referring to the recovery menu item 'apply update from external storage', as it asks for an img file. but maybe if my img file is not a system update but only a cwm img, then i brick my device. so i need some exact advice about this.
is there no workaround when nvflash sais that cannot write usb? in the nvflash useful topic they write something about if the usb is set to writeable but i don't know where to check/set this in win7.
also when in the apx mode i did not try adb, could adb work? (i will try this, but seems improbable)
thanks so far
if the bootloader is locked then it is locked and you can not use nvflash.
I am almost 100% sure that the update in the revoery is meant for system updates and not for recovery updates.
Did you try to do a factory reset?Not sure it will help but worth a try. And i think that it does not wipe the data on the internal sd.
about the usb write failed i can not offer any advice.I think that means that the booloader is locked.
berbecverde said:
if the bootloader is locked then it is locked and you can not use nvflash.
I am almost 100% sure that the update in the revoery is meant for system updates and not for recovery updates.
Did you try to do a factory reset?Not sure it will help but worth a try. And i think that it does not wipe the data on the internal sd.
about the usb write failed i can not offer any advice.I think that means that the booloader is locked.
Click to expand...
Click to collapse
thanks. i thought factory reset will wipe all data (except if i already have cwm). in any case i will have to try this at the end, and i am also pretty sure that factory reset will help - either losing all data or at least saving the data on the internal sd.
in any case i wait for a few more days in case somebody has some magic trick.
http://forums.androidcentral.com/lenovo-android-tablets/239622-lenovo-thinkpad-tablet-wont-boot.html
berbecverde said:
http://forums.androidcentral.com/lenovo-android-tablets/239622-lenovo-thinkpad-tablet-wont-boot.html
Click to expand...
Click to collapse
before doing the factory reset i searched for more info about nvflash.
given that we may have an 'sbk' code, is there some way to get data with nvflash?:
http://rootzwiki.com/topic/7593-bootloader/
and the perhaps good sbk code for tpt:
0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55
see also
http://forum.xda-developers.com/showthread.php?t=1745450&page=5
i think that the sbk code is for the ideapad not for the thinkpad, but you can give it a try.
berbecverde said:
i think that the sbk code is for the ideapad not for the thinkpad, but you can give it a try.
Click to expand...
Click to collapse
i don't know, maybe. still, for using nvflash with sbk there are some additional files and info needed according to that page which i don't know where to get. or how can i try it?
"For devices that use the Tegra's Secure Boot Key (SBK) feature, it is necessary to provide this key as an nvflash argument."
So in theory the commands are the same but you have to specify the sbk.
berbecverde said:
"For devices that use the Tegra's Secure Boot Key (SBK) feature, it is necessary to provide this key as an nvflash argument."
So in theory the commands are the same but you have to specify the sbk.
Click to expand...
Click to collapse
i added --sbk and then the code but then it said that incorrect parameter or something like that, so it seemed that --sbk is not a recognized parameter. did i use a bad version of nvflash maybe?
it is posible, you shoud search for a thread were they use the --sbk argument and try that version of nvflash
Would be news for me that we have the SBK from TPT
As I said I think the Sbk is for the idea pad
Sent from my HTC EVO 3D X515m using xda premium
berbecverde said:
As I said I think the Sbk is for the idea pad
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
i can confirm that it does not work, i tried this sbk with another nvflash, now the --sbk part was ok seemingly but still 0x4 error. so probably the sbk is indeed for the idea pad. it is so stupid that i loose all data just because lenovo does not give out sbk even after dropping support evidently.
factory reset is what comes, no other options.
thanks for all you people for the advices.
AW: [Q] urgent! stuck in bootloop, how to save data? (cwm? nvflash?)
Hi,
I'm from germany and I own a tablet which is the same hardware as K1, but selled under differnt name.
The nvflash for K1 doesn't work for me, because of different sbk? Don't know.
But I can flash particular partitions.
Maybe this will work for you too.
Please check first if you can read the partitiontable.
More can be found here:
w-w-w.avi-plus.com/repair-tips-forum/miscellaneous-software/android-english/nvflash-with-the-medion-lt-p9516-tablet.html
I'm not allowed to post links, please change "w-w-w" from the above link to "www".
Micky
Sent from my MD_LIFETAB_P9516 using xda app-developers app
Ameisentaetowierer said:
Hi,
I'm from germany and I own a tablet which is the same hardware as K1, but selled under differnt name.
The nvflash for K1 doesn't work for me, because of different sbk? Don't know.
But I can flash particular partitions.
Maybe this will work for you too.
Please check first if you can read the partitiontable.
More can be found here:
w-w-w.avi-plus.com/repair-tips-forum/miscellaneous-software/android-english/nvflash-with-the-medion-lt-p9516-tablet.html
I'm not allowed to post links, please change "w-w-w" from the above link to "www".
Micky
Sent from my MD_LIFETAB_P9516 using xda app-developers app
Click to expand...
Click to collapse
thanks, sounds interesting, yet it is too late, i already made a factory reset, so probably i won't risk and spend time on playing around with it. yet if somebody does, i would be interested whether it worked.
berbecverde said:
i think that the sbk code is for the ideapad not for the thinkpad, but you can give it a try.
Click to expand...
Click to collapse
Hi mnb123123.
I'm experiencing the same problem with a Thinkpad Tablet. The "recovery" menu is broken (/missing cache). I can not do a factory reset. And nvflash is disconnecting me on Windows when I execute the nvflash command.
Here it is my suffering thread.
Related
while trying to root and unlock bootloader on acer a500, somehow i screwed things up and had to finally flash a euu file to get it working again, now im rooted unlocked, i guess, im able to flash roms but my storage has been reduced to 128mb. , no matter what i flash or try no change, not enuff room to restore any apps.. question is any chance or anything i can do to recover that space? thank you...
athack said:
while trying to root and unlock bootloader on acer a500, somehow i screwed things up and had to finally flash a euu file to get it working again, now im rooted unlocked, i guess, im able to flash roms but my storage has been reduced to 128mb. , no matter what i flash or try no change, not enuff room to restore any apps.. question is any chance or anything i can do to recover that space? thank you...
Click to expand...
Click to collapse
Wow, you might have screwed the pooh on this one.
Did you install the V8 or 9 Unlocked bootloader?
Ok, for starters, WHICH EUU and what is current operating system?
Did you flash a custom Recovery (in this case CWM)? If so, what version?
But BEFORE you do anything else, you should get your UID number from Civato's sticky thread or one of the others. Very important. So check the sticky threads, there's a simple app to get your UID. Save it somewhere in like Notepad.
Then report back.
ok let me say ive been rooting my ohones since the OG droid, its been 5 or 6 diff since then but this tablet has me stumped... can you please tell me how i can find which version bootloader? the euu file i got off of tegra forum owners, ive got cwm based recovery v5.5.0.x 9thor2002ro rev 1.7) and as far as operating system ive flashed 3 diff roms so far the 1 im on now is flex resurection rev1...4.0.4 android version, ive tried 4.0.3, and jb... i have cpuid if thats the same as uid#...? if you could help in any way its much appreciated...
Moscow Desire said:
Wow, you might have screwed the pooh on this one.
Did you install the V8 or 9 Unlocked bootloader?
Ok, for starters, WHICH EUU and what is current operating system?
Did you flash a custom Recovery (in this case CWM)? If so, what version?
But BEFORE you do anything else, you should get your UID number from Civato's sticky thread or one of the others. Very important. So check the sticky threads, there's a simple app to get your UID. Save it somewhere in like Notepad.
Then report back.
Click to expand...
Click to collapse
when i run recovery bootlader version says 03.11 custom mode????
athack said:
ok let me say ive been rooting my ohones since the OG droid, its been 5 or 6 diff since then but this tablet has me stumped... can you please tell me how i can find which version bootloader? the euu file i got off of tegra forum owners, ive got cwm based recovery v5.5.0.x 9thor2002ro rev 1.7) and as far as operating system ive flashed 3 diff roms so far the 1 im on now is flex resurection rev1...4.0.4 android version, ive tried 4.0.3, and jb... i have cpuid if thats the same as uid#...? if you could help in any way its much appreciated...
Click to expand...
Click to collapse
Ha ha, no mate. No doubt you are a bit familiar. Phones is different than tabs though.
Ok,, when you start your tab normally, you should see the bootloader version. Upper left corner.
There's only a couple EUU files, and I believe both are Honeycomb.
CWM ver is ok.
But if you are running ICS or JB roms, on a HC bootloader, than that's not OK.
So, I need current ROM and version, and current bootloader version. Civato has several roms.
Just wanna see where exactly you are at right now.
MD
EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 Bundle (Stock 3.0.1 if I remember correctly) ...... FLEX-Resurrection_Rev1-Aroma-Public....0.03.11 ICS bootloader custom mods...
Moscow Desire said:
Wow, you might have screwed the pooh on this one.
Did you install the V8 or 9 Unlocked bootloader?
Ok, for starters, WHICH EUU and what is current operating system?
Did you flash a custom Recovery (in this case CWM)? If so, what version?
But BEFORE you do anything else, you should get your UID number from Civato's sticky thread or one of the others. Very important. So check the sticky threads, there's a simple app to get your UID. Save it somewhere in like Notepad.
Then report back.
Click to expand...
Click to collapse
athack said:
when i run recovery bootlader version says 03.11 custom mode????
Click to expand...
Click to collapse
3.11 sounds like an HC bootloader, or one of Skrilax_cz's initial bootloader. If you try running ICS or JB based roms, you're gonna get a lot of screwy stuff going on, Like display glitches and stuff.
You need to goto Civato's Bootloader thread in the Dev forum, and try running the apps listed there to get you to Skirlax_cz's unlocked bootloader for ICS. Works for CM JB.
@dibb_nz also has a thread there, explaining things about UID and stuff.
Then, after you get the unlocked bootloader NV flashed, throw CWM on there. I use 1.7.3 I believe. In mounts and storage, there is an option to format your internal SD. Select the option, then do your wipes and formats. Then flash the rom.
Think you'll be okay then.
recovery also says thor kernal v1.16mini running itsmagic that is on the screen when i run a backup....
athack said:
EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 Bundle (Stock 3.0.1 if I remember correctly) ...... FLEX-Resurrection_Rev1-Aroma-Public....0.03.11 ICS bootloader custom mods...
Click to expand...
Click to collapse
athack said:
recovery also says thor kernal v1.16mini running itsmagic that is on the screen when i run a backup....
Click to expand...
Click to collapse
It's magic is no longer needed for unlocked bootloader and ICS/JB.
If you boot holding PWR and Vol -, you should boot into the V8 bootloader menu. If you don't, there's an issue.
ok i got that set up right now, its magic is no longer needed it says... everything is working fine but still only 128 mb of storage wiped mounted unmounted formatted everything, nothing is changing it....
Moscow Desire said:
It's magic is no longer needed for unlocked bootloader and ICS/JB.
If you boot holding PWR and Vol -, you should boot into the V8 bootloader menu. If you don't, there's an issue.
Click to expand...
Click to collapse
Well, sounds like the emmc memory is hosed. As you read in the threads, it happens sometimes.
However, as a last chance, there is a thing called "bab sector". I've never used it before. Supposedly helps recover bad memory blocks. I've tried searching for it here in the forums, but must not be using the right search parameters . Found discussions on it in @Skrilax_CZ bootloader thread. It's labeled for the a501 but doesn't matter as partitions are the same I believe. He knows more about the memory partitions, so may want to post the issue in his bootloader thread.
But, I do happen to have one of the zips on my Dev Host server.
http://d-h.st/iQX
If I remember correctly, there are 2 variants of this repair file. @dibb_nz might know more about it.
Also on my server. is an HC roll back tool. If not mistaken, it may have a different variant of EUU. Might wanna run it and see if it resets partitions. As it seems like things screwed up when you ran an EUU.
http://d-h.st/0x7
At any case, I would run the EUU again. Can't hurt, and maybe will reset partitions.
thank you that bab sector file how would i go about installing that? flash with the a500 apx flash tool ? and the euu i believe get done that way also?
Moscow Desire said:
Well, sounds like the emmc memory is hosed. As you read in the threads, it happens sometimes.
However, as a last chance, there is a thing called "bab sector". I've never used it before. Supposedly helps recover bad memory blocks. I've tried searching for it here in the forums, but must not be using the right search parameters . Found discussions on it in @Skrilax_CZ bootloader thread. It's labeled for the a501 but doesn't matter as partitions are the same I believe. He knows more about the memory partitions, so may want to post the issue in his bootloader thread.
But, I do happen to have one of the zips on my Dev Host server.
http://d-h.st/iQX
If I remember correctly, there are 2 variants of this repair file. @dibb_nz might know more about it.
Also on my server. is an HC roll back tool. If not mistaken, it may have a different variant of EUU. Might wanna run it and see if it resets partitions. As it seems like things screwed up when you ran an EUU.
http://d-h.st/0x7
At any case, I would run the EUU again. Can't hurt, and maybe will reset partitions.
Click to expand...
Click to collapse
athack said:
thank you that bab sector file how would i go about installing that? flash with the a500 apx flash tool ? and the euu i believe get done that way also?
Click to expand...
Click to collapse
Ok, never run the Bab tool before. But looking at it, you have to be in APX mode just as you would to run NVFlash, as it operates the same way.
With the Bab tool, if it errors out writing any of the partitions, it should at least generate an error message. Now, you'll have to search to find out how to manually get into APX mode. But if I'm not mistaken, it's tab off. Hold PWR and Reset button. Then count to 3 or 5, release reset, then 2 counts later release PWR. But please do not quote me on this. Been some time, and primarily I work on the A701 now. But it's pretty close.
Then, run the bat file in the zip via a command window. Note I have never had to use this before.
The rollback/EUU works just like any other EUU. Has an exe file in it to run (make sure USB debugging is on, and remember to get your UID.
I also have an ATT EUU handy. Not sure which version it installs, but will be HC.
I still say to post a note in the Bootloader thread. Skrilax_cz knows more about the 50x partitions than even Acer.
flashed the bab file thru cmd promots device said pass reboot... rebooted to booloade mode saying error invalid primary lnx kernal image.. wont d...o anything but reboot to this same screen... also the other file euu is a rar file wont let me do anything with it when i flashed the other file euu i used the a500 tool and it found the euu file, how do i extract the euu from the roll back rom?
Moscow Desire said:
Ok, never run the Bab tool before. But looking at it, you have to be in APX mode just as you would to run NVFlash, as it operates the same way.
With the Bab tool, if it errors out writing any of the partitions, it should at least generate an error message. Now, you'll have to search to find out how to manually get into APX mode. But if I'm not mistaken, it's tab off. Hold PWR and Reset button. Then count to 3 or 5, release reset, then 2 counts later release PWR. But please do not quote me on this. Been some time, and primarily I work on the A701 now. But it's pretty close.
Then, run the bat file in the zip via a command window. Note I have never had to use this before.
The rollback/EUU works just like any other EUU. Has an exe file in it to run (make sure USB debugging is on, and remember to get your UID.
I also have an ATT EUU handy. Not sure which version it installs, but will be HC.
I still say to post a note in the Bootloader thread. Skrilax_cz knows more about the 50x partitions than even Acer.
Click to expand...
Click to collapse
thanks i found the tool in the rollback rom to redo my tab it restored my tab to full storage your a genius... thank u for all your help truly appreciate it...
athack said:
thanks i found the tool in the rollback rom to redo my tab it restored my tab to full storage your a genius... thank u for all your help truly appreciate it...
Click to expand...
Click to collapse
Ehhhh.... sometimes MD is just lucky I guess
CCR... I Put a Spell on You.... (what I'm listening to now) on a Viper4Android tricked out A701 running Evil Alex Purgatory V2 for the 701 :good:
Damn glad you got it going Mate!
Rock On!
MD
While attempting to flash a modified OTA flashable zip I managed to disable the touchscreen by NOT flashing thee important binary blob leaving me in a permanent apx mode and booting into android OS without a functioning touchscreen, Since the update is to 4.3 the device requests permission for adb so no adb reboot recovery... Also cannt access fastboot just apx mode
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Shaky156 said:
While attempting to flash a modified OTA flashable zip I managed to disable the touchscreen by NOT flashing thee important binary blob leaving me in a permanent apx mode and booting into android OS without a functioning touchscreen, Since the update is to 4.3 the device requests permission for adb so no adb reboot recovery... Also cannt access fastboot just apx mode
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Click to expand...
Click to collapse
Good and bad news, but an horizon... Thumbs up Shaky. Can't wait as similar problem to you.
Note
For those who are having problems with ADB/Fastboot commands not working correct on NT7, update them to r16.01
Linux Kernel for SHIELD (and Tegra Note 7) https://github.com/linux-shield/kernel
Shaky156 said:
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Click to expand...
Click to collapse
What happens if one "nvflash --create", would that take one to the recover straight after boot or is the recovery partition also wiped?
e8hffff said:
What happens if one "nvflash --create", would that take one to the recover straight after boot or is the recovery partition also wiped?
Click to expand...
Click to collapse
Nvflash currently doesnt support tegra 4 or atleast looks like that to me as it hangs on rcmver, doesnt pass that, will test... Also that doesnt take you to recovery it formats everything
Shaky156 said:
Nvflash currently doesnt support tegra 4 or atleast looks like that to me as it hangs on rcmver, doesnt pass that, will test... Also that doesnt take you to recovery it formats everything
Click to expand...
Click to collapse
You mahybe correct. The best I could get out of it was reporting my chip UID. Hasn't the Shield users been using nvflash?
e8hffff said:
You mahybe correct. The best I could get out of it was reporting my chip UID. Hasn't the Shield users been using nvflash?
Click to expand...
Click to collapse
Afaik shield users havent been using nvflash
Progress has been made on this...
EDIT: same issue though reading uid fails
EDIT2: Although i have the correct files apart from nvflash, I Talked to someone from nvidia, they have but wont release the nvflash cmd tool for tegra note 7, it wont happen, thread can close
Thread closed at the request of the OP.
MD
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
ssvNormandy said:
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
Click to expand...
Click to collapse
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
9918
Moscow Desire said:
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
Click to expand...
Click to collapse
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
ssvNormandy said:
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
Click to expand...
Click to collapse
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Moscow Desire said:
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Click to expand...
Click to collapse
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
ssvNormandy said:
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
Click to expand...
Click to collapse
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Moscow Desire said:
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Click to expand...
Click to collapse
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
ssvNormandy said:
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
Click to expand...
Click to collapse
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Moscow Desire said:
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Click to expand...
Click to collapse
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
ssvNormandy said:
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
Click to expand...
Click to collapse
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Moscow Desire said:
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Click to expand...
Click to collapse
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
ssvNormandy said:
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
Click to expand...
Click to collapse
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Moscow Desire said:
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Click to expand...
Click to collapse
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
ssvNormandy said:
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
Click to expand...
Click to collapse
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Moscow Desire said:
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Click to expand...
Click to collapse
blackthunder's tool just WILL NOT RUN on the tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
ssvNormandy said:
blackthunder's tool just WILL NOT RUN on my tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
Click to expand...
Click to collapse
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Moscow Desire said:
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Click to expand...
Click to collapse
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
ssvNormandy said:
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
Click to expand...
Click to collapse
Yep, same issue with me. I'm stuck on 3.2 HC
Well, it's a secondary tablet anyhow.
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
ssvNormandy said:
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
Click to expand...
Click to collapse
Yeah, and a little bit of knowledge :laugh::laugh::laugh: (maybe too much)
Am glad I could help out!! :good:
Hi all,
I wanted to unroot and factory reset the phone. I forgot to flick that "enable oem unlocking" button, I tried "flash-all" directly on bootloader and it didn't work and after reboot it got stuck on Google screen. I waited for a while but nothing happened. I wiped system, vendor, cache... Nothing.
I have this message for every parts of the factory image:
Code:
FAILED (remote: device is locked. Cannot flash images)
As i said, the same error appear for boot.img, recovery.img and system.img.
Now, I can still use my "old" TWRP and push files through adb, i tried to flash a ROM (to check that "enable oem unlocking slider") trough ADB sideload, but the flash fails because recovery can't mount "boot", "system" and "vendor".
Any ideas?
If can help anytime I run the recovery, i got a "enter password" option to decrypt data.
Hitting cancel, TWRP ask me if i want to keep system read only or not, what do i have to do?
I tried to perform a full wipe, but i got this error in the terminal:
Code:
E:Failed to decrypt data.
E:Unable to decrypt with default password.
E:You may need to perform a Format Data.
Updating partition details...
E:Unable to mount '/vendor'
...done
E:Unable to mount storage.
Full SELinux is present.
E:Unable to mount setting storage during GUI startup.
E:Failed to wipe dalvik
Updating partition details...
E:Unable to mount '/vendor'
...done
E:Unable to mount storage.
Did i damaged something?
There's basically nothing you can do. You can't flash anything with a locked bootloader, and you can't unlock your bootloader because you can't boot into the OS. There's one thing you can try, try using adb sideload in TWRP to flash a ROM, any ROM, just to get it booting again. That's your only option at this point. If you don't know to use adb sideload just search on Google.
Heisenberg said:
There's basically nothing you can do. You can't flash anything with a locked bootloader, and you can't unlock your bootloader because you can't boot into the OS. There's one thing you can try, try using adb sideload in TWRP to flash a ROM, any ROM, just to get it booting again. That's your only option at this point. If you don't know to use adb sideload just search on Google.
Click to expand...
Click to collapse
Thanks for your kind answer mate, but i have a little problem: when i try to sideload something, i get stuck at 45 %, then the sideload fails and i can hear a "disconnected" sound from Windows 10...
Keep trying different ROM files and hope for the best. I really hope it works out for you
Monster_Joe said:
Thanks for your kind answer mate, but i have a little problem: when i try to sideload something, i get stuck at 45 %, then the sideload fails and i can hear a "disconnected" sound from Windows 10...
Click to expand...
Click to collapse
Like the other guy said, you gotta keep trying, this is the only thing that's going to save your phone.
If your device is based on MTK chipset you can use SP flash tool
Tapan98 said:
If your device is based on MTK chipset you can use SP flash tool
Click to expand...
Click to collapse
Hi, thanks for your answer, can you be more specific?
How can I check if my phone has this chipset?
Heisenberg said:
Like the other guy said, you gotta keep trying, this is the only thing that's going to save your phone.
Click to expand...
Click to collapse
So basically i have two options:
- adb push
- adb sideload
It's correct?
Monster_Joe said:
How can I check if my phone has this chipset?
Click to expand...
Click to collapse
It doesn't
Tapan98 said:
If your device is based on MTK chipset you can use SP flash tool
Click to expand...
Click to collapse
Why would you even post this? Probably best not to give advice if you know nothing about the device.
Monster_Joe said:
Hi, thanks for your answer, can you be more specific?
How can I check if my phone has this chipset?
Click to expand...
Click to collapse
It doesn't, you can ignore that post.
Monster_Joe said:
So basically i have two options:
- adb push
- adb sideload
It's correct?
Click to expand...
Click to collapse
From I can tell, you can't access the internal storage while in TWRP, which would render adb push useless. I believe all you can do is adb sideload, if that doesn't work you'd need to get it repaired.
Heisenberg said:
From I can tell, you can't access the internal storage while in TWRP, which would render adb push useless. I believe all you can do is adb sideload, if that doesn't work you'd need to get it repaired.
Click to expand...
Click to collapse
Hi Heisenberg, thanks for your help, is really appreciated.
As far as i know, i can mount /sdcard partition and adb push files there... Or i'm wrong?
By the way I will try when back at home!
Monster_Joe said:
Hi Heisenberg, thanks for your help, is really appreciated.
As far as i know, i can mount /sdcard partition and adb push files there... Or i'm wrong?
By the way I will try when back at home!
Click to expand...
Click to collapse
Thinking about it more, of TWRP can't mount system then it won't be able to flash a ROM. It's worth a try though.
Heisenberg said:
Why would you even post this? Probably best not to give advice if you know nothing about the device.
Click to expand...
Click to collapse
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Tapan98 said:
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Click to expand...
Click to collapse
well... while you're trying to help, you can make matters worse for some if you arent giving device specific instructions.
tho in the this case, odds are more damage can't be done... fortunately/unfortunately.
Don't take it personally. We all make mistakes. You meant well!
Tapan98 said:
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Click to expand...
Click to collapse
With a little search on Google i found this thread ---->http://forum.xda-developers.com/nexus-6/help/unlock-bootloader-os-installed-t3070473
This guy had the (sort of) same issue with the Nexus 6.
Maybe it's totally useless to your situation, but i guess it never hurts to see how he fixed it.
I'm not entirely sure i understand how he did it.
You'll need a backup though.
Tapan98 said:
Hey, sorry for that, i'm newbie to this forum (probably first post on this forum), I didn't saw which device it was. And don't be so mean
Click to expand...
Click to collapse
My intention wasn't to be mean, but what I said is true. If you give incorrect advice for a device that you have no experience with, the user could end up with a bricked phone. I doubt you want to be responsible for that. Your intentions were good, but stick to what you know, accuracy is of utmost importance here on XDA.
Very interested in seeing the outcome to this situation. Best of luck @Monster_Joe!!!
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
My problem is that it does not unlock OEM and I was not active debugging, the phone just let me enter Fastboot but at the time of choosing RECOVERY it restarts
emmafer44 said:
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
Click to expand...
Click to collapse
Dude try Nexus toolkit my Wugfresh (NRT Toolkit) you have to boot to bootloader and use the application to clean install
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Alot of users are facing this bootloop issue. So far no one has been able to figure out a pattern that will give us insight into what kind of devices might be affected by this issue. I have created this survey on GoogleForums so far there are very few responses. Please participate to help the community figure out the probable cause for this bootloop
https://docs.google.com/forms/d/1nGAVdnjbkOE1ohvZvqbntb_7afT4p2OzbFIJjJWiy9Q/edit?c=0&w=1
BTW what's your phone's manufacturing date? were you using Magisk or SuHide?
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
v12xke said:
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Ive tried literally every fix, its dead jim.
Dadud said:
Ive tried literally every fix, its dead jim.
Click to expand...
Click to collapse
Have you tried FORMATTING boot, system, data & vendor and then reflash? Format, not erase/wipe. Move your TWRP backup off to PC and try that. If you are rusty in ADB/Fastboot, then use NRT to do same in advanced tools. If you have a working recovery and your bootloader is unlocked, I would not give up yet. Good luck!
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
rchtk said:
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
Click to expand...
Click to collapse
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
You never know the level of the person you're talking about eh. Just tought you hadn't tried the dd.
So dd shutting down before completing wasn't expected but now if I read again your posts, you said doing a photo shuts down the phone and that's quite typical of power related problems. Sh*t.
Could be the battery not holding discharge. Can the device stay in twrp with screen off? Did you try to let it fully discharge and charge it with a slow charge?
There are a lot of information in /sys/ or dmesg but it won't solve your issue.
Still under warranty?
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
Forget restoring your backup for now. You're not a noob, so transfer your TWRP backup to PC, then FORMAT each partition first, including userdata and then reflash using a Google Imagehere. Ensure you are using the latest version of ADB/Fastboot. You didn't mention you have already attempted to Fastboot flash the NMF26F image. What was your result then? The reason I'm asking is that the Google script erases the partitions- does not format, but running the script will tell you which partition failed during writing.
Huawei Customer Service!!
Had the exact same problem creep up on me this past weekend. I ended up calling Huawei and they are doing a free warranty repair on my phone even though I'm almost two months out of warranty.
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Tylog said:
Make sure you are on SDK 25...
Click to expand...
Click to collapse
Yes, the latest ADB / Fastboot is required. The rest of the SDK is not mandatory. You can get a minimalist ADB-Fastboot-Driver install from an XDA dev here.
Also, TWRP updated for Angler recently here. This update solved a persistent backup problem I had with the previous v3.0.2-2
bought it second hand, and the previous owner bought it at launch, so im just a month or so out of warranty. im trying to get the original receipt to attempt to RMA it. Huawei's IMEI lookup says its under warranty till april 4th next year.
Tylog said:
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Click to expand...
Click to collapse
Was your phone stuck in Bootloop of death as well? How did you fix it? What do think causes this issue and how can it be avoided?