Related
First of all, hello. I'm new to tinkering with Android, but I've flashed firmware on dumbphones 68 ways to Sunday, so I'm not new to phone modding nor am I worried about technical answers, so fire away.
To start, this phone has not been rooted (yet) and has the stock 2.3.4 ROM.
I've screwed around for the last six hours or so in fear of bricking the phone only to realize I should have followed a different set of instructions after Step 1 of Downgrading in this guide, because now that I've read other guides, I find this one unnecessarily complicated compared to directly pushing PD15IMG.zip to sdcard.
Since I'm already calling it quits on going any farther with this tonight, I just need a few questions answered before I give this another shot.
1. Is ADB supposed to see the phone when it is in recovery or bootloader mode? When the phone is in recovery or bootloader, entering adb devices in the Windows Command Prompt returns an empty list of devices attached.
2. I have the bad eMMC in my phone. In addition, once in recovery mode and I press Vol Up+Power, I see an error message that says E:Can't open /cache/recovery/command. I also get additional "can't open" error messages when I select Wipe data/factory reset from the recovery menu:
Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete...
Are those errors a concern? Are they a product of a failed eMMC or a corrupted file system? If they are because of the eMMC, would it be safe to say that I should leave this phone alone? If they are because of the file system, what I can do to fix these errors?
3. Now that I've read other, more MT4G-specific downgrading guides, will pushing PD15IMG.zip to sdcard and fastboot take care of the "can't open" errors in question 2 as well?
you need clockwork recovery if you want to flash.
You need to downgrade then root with s-off and have eng bootloader to attempt the wipes you've been trying. I just downgraded, last night, just follow the instructions. It's really easy. don't see how you can brick the phone while downgrading unless your phone dies during the flashing step.
Btw you shouldn't worry too much about the bad chip. Both good and bad have been known to brick. All bad chips aren't bad, it's only more susceptible to bricking. I have a bad chip and been flashing since forever
Sent from my HTC Glacier using XDA App
Snakecharmed said:
First of all, hello. I'm new to tinkering with Android, but I've flashed firmware on dumbphones 68 ways to Sunday, so I'm not new to phone modding nor am I worried about technical answers, so fire away.
To start, this phone has not been rooted (yet) and has the stock 2.3.4 ROM.
I've screwed around for the last six hours or so in fear of bricking the phone only to realize I should have followed a different set of instructions after Step 1 of Downgrading in this guide, because now that I've read other guides, I find this one unnecessarily complicated compared to directly pushing PD15IMG.zip to sdcard.
Since I'm already calling it quits on going any farther with this tonight, I just need a few questions answered before I give this another shot.
1. Is ADB supposed to see the phone when it is in recovery or bootloader mode? When the phone is in recovery or bootloader, entering adb devices in the Windows Command Prompt returns an empty list of devices attached.
2. I have the bad eMMC in my phone. In addition, once in recovery mode and I press Vol Up+Power, I see an error message that says E:Can't open /cache/recovery/command. I also get additional "can't open" error messages when I select Wipe data/factory reset from the recovery menu:
Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete...
Are those errors a concern? Are they a product of a failed eMMC or a corrupted file system? If they are because of the eMMC, would it be safe to say that I should leave this phone alone? If they are because of the file system, what I can do to fix these errors?
3. Now that I've read other, more MT4G-specific downgrading guides, will pushing PD15IMG.zip to sdcard and fastboot take care of the "can't open" errors in question 2 as well?
Click to expand...
Click to collapse
are you talking about the stock recovery? because the stock recovery is supposed to say "E: can't open /cache/recovery/command". not sure why but it does. happened on every stock recovery i've seen.
Yes, I'm on stock recovery, and that's good to know that it appears to be normal.
Currently, I have successfully downgraded to stock 2.2.1 with the .86 bootloader.
Now, in following this guide, I've gotten to the end of Step 10 and I get the following:
Code:
[B]# ./gfree -f[/B]
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g899d047
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a63a4, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a6000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a63a4 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-1319315128.bin
...
Error opening backup file.
What should I do with the backup not being written?
Upon rebooting into bootloader, it still says S-ON.
Also, to back up a bit, in Step 5, I was supposed to unplug the phone from the computer and use the Android Terminal Emulator. I didn't and executed the commands through ADB because the soft keyboard input wasn't working at all in Android Terminal Emulator.
EDIT: Fixed the problem with backup not working and I now have S-OFF. The microSD card in my phone wasn't being detected properly, so instead of seeing the correct permissions d---rwxr-x with ls -l for directory /mnt/sdcard, it was being seen as read-only. When gfree attempted to write the backup to /sdcard, it failed because the SD was read-only.
I took out my 16GB card and put in my 8GB and this time, the gfree backup saved. I can't recall if I had the phone plugged in when I rebooted the phone or plugged it in afterward, but I'm slowly realized that the SD card gets remounted when you plug and unplug the phone from the computer due to the different file systems. That's why I had issues saving files to /sdcard through ADB. Now I understand why the commands were supposed to be entered in Android Terminal Emulator, but I couldn't get the soft keyboard to function in it. Hopefully, that won't be a problem after flashing the new ROM, but that will be the next concern for me.
EDIT 2: I have now installed CWM Recovery 5.0.2.0. Also, it looks like the Android Terminal Emulator developer borked the keyboard input with today's update. Read comments from October 22, 2011:
https://market.android.com/details?id=jackpal.androidterm&hl=en
remember to perm root your phone and flash the engineering bootloader i think it was like .85 something
Thanks. I had it perm-rooted and installed the engineering bootloader by the end of the weekend. I'm looking forward to flashing VU after I get some more free time and take note of settings and apps I might want to keep from the stock ROM.
your apps should be restored by google
but just in case, use titanium backup or my backup. I personally prefer my backup to backup my sms/mms, apps and settings because its quicker when you restore.
I use titanium backup to backup and restore system apps.
Oh yeah you shouldn't try to backup your settings from your stock and restore it when you flash VU, they're different OS so might cause problems. BUT it's useful when you flash new updates.
Other than VU, you might want to try TDJ's Darkside if you want to test out sense 3.5. However, i might go back to virtuous once they release a final build for sense 3.5
happy flashing
I actually didn't have any settings to back up because I haven't been using the phone as my primary phone since I bought it, but I backed up the stock Froyo ROM and flashed to VU 2.39 two nights ago. Everything appears to be running well. I reinstalled Swype 3.7 from the stock Gingerbread ROM and I still need to reinstall Genius with Button Shortcut.
I don't really like the trouble of going back and forth between ROMs, so thankfully, I'm quite pleased with VU and Sense 3.0. The rest is just customization at this point. I may eventually take a look at Virtuous Trentacinque after it goes gold, but I didn't want to wait around for it nor run a beta ROM on what will soon become my main phone. I have no problem with flashing files and making tweaks all day, but it gets old after a while and I'd rather just use the equipment instead.
So far, battery life on VU seems to be pretty good and is much better than stock. I'm enjoying the new ROM so far as well as finally getting to use the phone rather than just backing up files and testing features.
fyi, Swype 3.25 beta is out. I think Swype 3.26 beta is out too. I think there was a thread with themed Swypes somewhere. But I forget.
Sent from my HTC Glacier using XDA App
This thread is just to direct all the noobs into the right direction, related to root and flash new roms in the Desire HD.
[*]Rooting and reverting to stock
Due to the retirement of the Hack Kit, rooting methods have been reduced to:
http://forum.xda-developers.com/showthread.php?t=2168500
or if you are skilled in using adb and fastboot commands:
http://tau.shadowchild.nl/attn1/?cat=6
If you are still stuck and want to revert your phone back to out of the box, then use Marsdta's Guide:
http://forum.xda-developers.com/showthread.php?t=1396229
or Gene Poole's Tool (that will revert also S-OFF):
http://forum.xda-developers.com/showthread.php?t=1208507
[*]Flashing a Custom Rom
To flash a custom rom you need to be rooted and S-OFF (if u used the Hack Kit) or have and unlocked bootloader using HTCDEV tool (wich I don't suggest)
Once u are S-OFF and have CWM or some other custom recovery installed (I personally prefer 4ext) you have to follow these steps (read the dev's thread about particularities. This is just a general guide on how to do it):
Download the custom rom .zip file and put it in your sdcard. Make sure that u check md5sum first just to avoid bootloops.
Reboot phone in recovery. There are many ways to do that, the first can be using Rom Manager (I don't suggest using it for anything else but that) and choosing reboot in recovery option. The second way is to boot in bootloader (press power down and reboot choosing hboot) or just turn phone off and power it up pressing power and volume down. And the last is to use adb commands. Plug the phone as charge only with usb debugging on, open a cmd as admin or terminal as root in your PC and then type adb reboot recovery.
Once in recovery, you need to do a full wipe (wipe data / factory reset and wipe cache + dalvik cache). You can also format some other partitions such as data and system, but the full wipe will work.
When full wipe is finished, go to flash zip from sdcard option, choose zip file and then flash that file.
Reboot the phone once it has finished flashing and wait for the device to fully reboot. The first boot will take a while (probably longer than usual) so don't get scared.
If you flashed a CM based rom, you need to flash google apps separately as well, so find the gapps file corresponding to your rom and flash it in the same manner as above described.
Trouble Shooting
Bootloops: If your phone repeats over and over the bootanimation, don't panic, you are not bricked. Something must have gotten wrong but you can reboot in recovery and re flash the rom as previously described. If bootloop is still there, then try downloading the zip again or choose a diffrent rom.
Factory Reset: If you factory reset the phone and you are not stock, then the phone won't have a rom...you will get stuck in the splash screen (white screen with the green HTC). Just do as described above, get a rom to the sdcard and then flash it. You are not bricked, you are just stuck
Well, this was just to try to point you in the right direction. If you think that I missed something, feel free to tell me and will add it to the OP.....Salud! :good:
Nice post man (although I'm already rooted ), it'd really help some new guys cause it goes straight to the thread. Mod's make this a sticky?
Sent from my Desire HD using Swype beta for Android!
GuyInTheCorner said:
Nice post man (although I'm already rooted ), it'd really help some new guys cause it goes straight to the thread. Mod's make this a sticky?
Sent from my Desire HD using Swype beta for Android!
Click to expand...
Click to collapse
Thanks...that is the idea of it...to help people and point the right direction...let's hope it does...
One one side you got guyinthecorner and on the other you got cyraxdroid.
Sent from a dream.
Teichopsia said:
One one side you got guyinthecorner and on the other you got cyraxdroid.
Sent from a dream.
Click to expand...
Click to collapse
I am surrounded....but that is good...:cyclops:
Shucks, I thought it didn't get posted. So are they.
I haven't had a chance to search for the tutorial you recomended, could you link me to it? Thanks in advance.
Sent from a dream.
Teichopsia said:
Shucks, I thought it didn't get posted. So are they.
I haven't had a chance to search for the tutorial you recomended, could you link me to it? Thanks in advance.
Sent from a dream.
Click to expand...
Click to collapse
Sorry buddy, but what tutorial are u talking about....so I can link it..
glevitan said:
Sorry buddy, but what tutorial are u talking about....so I can link it..
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
Click to expand...
Click to collapse
Once I get back home in a couple weeks I'll start practicing. Well, probably ina month or so if I'm honest to myself.
Sent from a dream.
Teichopsia said:
Once I get back home in a couple weeks I'll start practicing. Well, probably ina month or so if I'm honest to myself.
Sent from a dream.
Click to expand...
Click to collapse
I guess this was the one....http://forums.acsyndicate.net/showthread.php?3369-TUTORIAL-Bootanimation-creation-amp-tools!
If not just let me know!
flash sabsa 8.0 to 8.5??
hello noobi here, just want to ask a step by step on how to upgrde from 8.0 to 8.5 sabsa? do i need to full wipe the 8.0? or just flash the 8.5 directly???
Pau Mckry said:
hello noobi here, just want to ask a step by step on how to upgrde from 8.0 to 8.5 sabsa? do i need to full wipe the 8.0? or just flash the 8.5 directly???
Click to expand...
Click to collapse
As always, you can dirty flash (only wipe cache and dalvik), but if you run into problems do a full wipe (system, data, and cache) before reporting any bugs.
thank you so much for the TS, i read this to root my first ever android device (DHD).... i got my device and straight away root it
thanks again
hey everybody!
i got a problem with downgrading my dhd. the aahk just stopped during the process. it downloaded the new ruu and successfully pushed it onto the sd card but after that it just stopped downgrading.
i dont know if i just can cancel the window or if that will damage my phone. i already read the effen manual but didnt find a solution.
i hope you can help me.
greetings from germany
Hotte175 said:
hey everybody!
i got a problem with downgrading my dhd. the aahk just stopped during the process. it downloaded the new ruu and successfully pushed it onto the sd card but after that it just stopped downgrading.
i dont know if i just can cancel the window or if that will damage my phone. i already read the effen manual but didnt find a solution.
i hope you can help me.
greetings from germany
Click to expand...
Click to collapse
please post the Hack Kit session in here...When you say that stopped downgrading means that your phone is in hboot and you have not been prompted to update or has started doing something in the phone and got stuck in the middle?
Ace Advanced Hack Kit [Linux/OSX/Windows] attn1 2011/2012
___________________________
MAIN MENU | |
| Only ONE Menu Step to: |
1 - Hack Ace <----------------------------+ * S-OFF |
| * SIM Unlock |
2 - DONATE (Encouraged, but optional) | * SuperCID |
| * Root |
| * Busybox |
| |
**********************************************************************
o - Options Menu (Return to Stock, Flash radios, etc)
**********************************************************************
t - Toggle Flash Method - current method is fastbootRUU
*********************************************************************
q - Quit
[Select and press Enter]1
3.12.405.1
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
[Would you like to downgrade? y/n]y
Download this RUU? [y,n]y
--2012-10-29 19:24:44--
Resolving tau.shadowchild.nl... 176.9.40.154
Connecting to tau.shadowchild.nl|176.9.40.154|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 259503624 (247M) [application/zip]
Saving to: `PD98IMG/PD98IMG-GB2.zip'
100%[======================================>] 259,503,624 682K/s in 6m 35s
2012-10-29 19:31:18 (642 KB/s) - `PD98IMG/PD98IMG-GB2.zip' saved [259503624/2595
03624]
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
2275 KB/s (259503624 bytes in 111.359s)
Setting up to temproot....
rm failed for /data/local/tmp/*, No such file or directory
441 KB/s (21215 bytes in 0.046s)
1789 KB/s (572752 bytes in 0.312s)
601 KB/s (19240 bytes in 0.031s)
going for temproot using zergRush....
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Error opening input file.
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
or to B. Kerler:
/dev/block/mmcblk1: cannot open for write: Permission denied
starting downgrade...
i hope that helps. got stuck about 1 1/2 hours ago. i may have to mention that i have a desire hd and not a inspire 4g. but according a german site that should not be an issue.
Hotte175 said:
Ace Advanced Hack Kit [Linux/OSX/Windows] attn1 2011/2012
___________________________
MAIN MENU | |
| Only ONE Menu Step to: |
1 - Hack Ace <----------------------------+ * S-OFF |
| * SIM Unlock |
2 - DONATE (Encouraged, but optional) | * SuperCID |
| * Root |
| * Busybox |
| |
**********************************************************************
o - Options Menu (Return to Stock, Flash radios, etc)
**********************************************************************
t - Toggle Flash Method - current method is fastbootRUU
*********************************************************************
q - Quit
[Select and press Enter]1
3.12.405.1
This version of Android cannot use the hack kit at this time.
You can downgrade if you like, then rerun the hack step.
WARNING: THIS WILL WIPE DATA
[Would you like to downgrade? y/n]y
Download this RUU? [y,n]y
--2012-10-29 19:24:44--
Resolving tau.shadowchild.nl... 176.9.40.154
Connecting to tau.shadowchild.nl|176.9.40.154|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 259503624 (247M) [application/zip]
Saving to: `PD98IMG/PD98IMG-GB2.zip'
100%[======================================>] 259,503,624 682K/s in 6m 35s
2012-10-29 19:31:18 (642 KB/s) - `PD98IMG/PD98IMG-GB2.zip' saved [259503624/2595
03624]
a67daa6baa7ef085307593fef6329d14 *PD98IMG/PD98IMG-GB2.zip
Flash the downgrade RUU? [y,n]y
pushing rom to sdcard - this takes time please be patient.
2275 KB/s (259503624 bytes in 111.359s)
Setting up to temproot....
rm failed for /data/local/tmp/*, No such file or directory
441 KB/s (21215 bytes in 0.046s)
1789 KB/s (572752 bytes in 0.312s)
601 KB/s (19240 bytes in 0.031s)
going for temproot using zergRush....
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
setting mainver lower for downgrade...
--set_version set. VERSION will be changed to: 1.31.405.6
Misc partition is "/dev/block/mmcblk0p17"
Patching and backing up misc partition...
Error opening input file.
Creating goldcard....
HTC android goldcard tool Copyright (C) 2011, Wayne D. Hoxsie Jr.
Original code by B. Kerler. Special thanks to ATTN1 and the XDA team.
Donations can be made to the Electronic Frontier Foundation:
or to B. Kerler:
/dev/block/mmcblk1: cannot open for write: Permission denied
starting downgrade...
i hope that helps. got stuck about 1 1/2 hours ago. i may have to mention that i have a desire hd and not a inspire 4g. but according a german site that should not be an issue.
Click to expand...
Click to collapse
Was your phone as charge only by default?? your sdcard was not accessible. Try rebooting the phone, and make sure that charge only is selected by default....
glevitan said:
Was your phone as charge only by default?? your sdcard was not accessible. Try rebooting the phone, and make sure that charge only is selected by default....
Click to expand...
Click to collapse
charge only was set by default checked it twice before starting. but i will try it again. but i dont have to install the htc drivers right?
just did it once again and it worked. now the device asks me if i want to update. does it mean that he wants to install the downgraded version?
Hotte175 said:
charge only was set by default checked it twice before starting. but i will try it again. but i dont have to install the htc drivers right?
just did it once again and it worked. now the device asks me if i want to update. does it mean that he wants to install the downgraded version?
Click to expand...
Click to collapse
Yes. It will be flashed twice. After that just re run the hack kit and you will be done
Sent from my GT-N7000 using xda app-developers app
isn't better to install the HTC drivers? so that you can connect thru adb too if needed...
at first i can't even boot into recovery and i used the adb command on my DHD
Oddly my google apps can't seem to function after flashing JellyTime on DHD. I won't repost here but if anyone can have a look here it would be great. Many thanks.
I'm having an odd problem with my A500, and while I've seen people with some of the symptoms I'm having, I haven't yet found anyone with all of them. I would appreciate any advice you all may have.
I purchased my A500 on the day it came out, so it's long out of warranty. Everything has been fine with it until two nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts, usually starting with Watchdog (the app killer I use), followed by calendar storage, and then a number of others. At that point, any app I opened would crash. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. I tried to factory reset but holding volume up, holding the power button, and continuing to hold volume up while switching the screen lock. The screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", nothing happens. The button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice?
Princepapa said:
I'm having an odd problem with my A500, and while I've seen people with some of the symptoms I'm having, I haven't yet found anyone with all of them. I would appreciate any advice you all may have.
I purchased my A500 on the day it came out, so it's long out of warranty. Everything has been fine with it until two nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts, usually starting with Watchdog (the app killer I use), followed by calendar storage, and then a number of others. At that point, any app I opened would crash. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. I tried to factory reset but holding volume up, holding the power button, and continuing to hold volume up while switching the screen lock. The screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", nothing happens. The button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice?
Click to expand...
Click to collapse
Well, first guess, you have corrupted data somewhere in one of the partitions (/System or /Data). I'm guessing /System as the issue continues after a factory reset, which is "supposed" to wipe the /Data partition.
I'll assume you are stock and un-rooted? Running stock ICS?
The first thing I would do, is while the tab is still running, get your UID number.
First goto Settings/Developer Options, and turn on USB Debugging.
Then go to the Development forum, and check the sticky about how to get your UID number. Should be a simple app you run from your PC while tab is connected. Write it down and save it somewhere (just in case)
Moscow Desire said:
Well, first guess, you have corrupted data somewhere in one of the partitions (/System or /Data). I'm guessing /System as the issue continues after a factory reset, which is "supposed" to wipe the /Data partition.
I'll assume you are stock and un-rooted? Running stock ICS?
The first thing I would do, is while the tab is still running, get your UID number.
First goto Settings/Developer Options, and turn on USB Debugging.
Then go to the Development forum, and check the sticky about how to get your UID number. Should be a simple app you run from your PC while tab is connected. Write it down and save it somewhere (just in case)
Click to expand...
Click to collapse
Thanks for the help!
Yes, I'm running stock, unrooted Android version 4.03.
I've installed blackthund3r's A500 Manager, and it detects my tablet, but it when I try to get my CUPID I get the error "system/bin/sh: su: not found".
I've downloaded "Afterota lite", but hesitate to use it because it says "USE WITH OTA ANDROID SYSTEMS ONLY" and I have no idea if that applies to me or not.
I'm assuming I'm ok to use it, but I don't want to take any chances.
Princepapa said:
Thanks for the help!
Yes, I'm running stock, unrooted Android version 4.03.
I've installed blackthund3r's A500 Manager, and it detects my tablet, but it when I try to get my CUPID I get the error "system/bin/sh: su: not found".
I've downloaded "Afterota lite", but hesitate to use it because it says "USE WITH OTA ANDROID SYSTEMS ONLY" and I have no idea if that applies to me or not.
I'm assuming I'm ok to use it, but I don't want to take any chances.
Click to expand...
Click to collapse
Since the 17th I have exactly all the same problems that you describe!!! I also have the same configuration. Did you may have also the following:
Current Image Version:
Acer_AV041_A500_1.062.00.EMEA_DE?
I did not find a solution so far. But I was able to recover the CUPID - not with the A500 Manager (A500Manager1.1.1) - that did not work. But by retrieving the acer_cpu_id from a file. I did it with adb tools and found it here:
/sys/firmware/fuse/acer_cpu_id
I have been able to get into APX mode (with blackthund3r_A500_APX_Flash_Tool_v0.4.1), but could not flash a new image. I could not get root (with ICS Root 7.2.0), by any method that I tried.
By every operation that I do - it always starts with the same app's and version that I had before. It seems like an "read only" system.
Hope you could solve that problem in the mean time.
Mratlan
Mratlan said:
Since the 17th I have exactly all the same problems that you describe!!! I also have the same configuration. Did you may have also the following:
Current Image Version:
Acer_AV041_A500_1.062.00.EMEA_DE?
I did not find a solution so far. But I was able to recover the CUPID - not with the A500 Manager (A500Manager1.1.1) - that did not work. But by retrieving the acer_cpu_id from a file. I did it with adb tools and found it here:
/sys/firmware/fuse/acer_cpu_id
I have been able to get into APX mode (with blackthund3r_A500_APX_Flash_Tool_v0.4.1), but could not flash a new image. I could not get root (with ICS Root 7.2.0), by any method that I tried.
By every operation that I do - it always starts with the same app's and version that I had before. It seems like an "read only" system.
Hope you could solve that problem in the mean time.
Mratlan
Click to expand...
Click to collapse
I'm sorry to hear that you have the same problem, though I'm kind of glad I'm not alone here.
My Image Version is: Acer_AV041_AA500_RV05RC01_PA_CUS1
"Read only" is a great description of this, in fact, I'm received errors indicating that it's a read only file when trying to resume my previous place in a video that I have saved on my SD card.
So you have not been able to get it to factory reset using external tools either?
Princepapa said:
I'm sorry to hear that you have the same problem, though I'm kind of glad I'm not alone here.
My Image Version is: Acer_AV041_AA500_RV05RC01_PA_CUS1
"Read only" is a great description of this, in fact, I'm received errors indicating that it's a read only file when trying to resume my previous place in a video that I have saved on my SD card.
So you have not been able to get it to factory reset using external tools either?
Click to expand...
Click to collapse
Correct. I could not do:
- a factory reset
- root the tablet
- use recover to make a downgrade
I try to write a new image with blackthund3r_A500_APX_Flash_Tool_v0.4.1. But it is very slow.
Hope we get some good idea's what else we could try.
Mratlan
Mratlan said:
Correct. I could not do:
- a factory reset
- root the tablet
- use recover to make a downgrade
I try to write a new image with blackthund3r_A500_APX_Flash_Tool_v0.4.1. But it is very slow.
Hope we get some good idea's what else we could try.
Mratlan
Click to expand...
Click to collapse
How slow is "very slow"? If it works, I'd be willing for it to take a long time...unless "very slow" means a few percent per day.
Princepapa said:
How slow is "very slow"? If it works, I'd be willing for it to take a long time...unless "very slow" means a few percent per day.
Click to expand...
Click to collapse
Well, I do not know. I had to start again, because I forgot to disable energy saver. Hence during the process there was a stop and I was forced to start again. So my estimation would be several hours (4-8h?).But I’m not sure if it will work.
If you try it again, please let me know how it goes. I probably won't be able to work on mine again until this weekend. I'm also going to continue to research other solutions, though it seems not many people have had this problem, and not many people have ideas for solutions...
Princepapa said:
If you try it again, please let me know how it goes. I probably won't be able to work on mine again until this weekend. I'm also going to continue to research other solutions, though it seems not many people have had this problem, and not many people have ideas for solutions...
Click to expand...
Click to collapse
The flash process (with blackthund3r_A500_APX_Flash_Tool_v0.4.1) did not come to an end.
I tried the following method as descriped here:
http://forum.xda-developers.com/showthread.php?t=2450119&highlight=formatting+partition+bct+failed
But without sucess - but at least I know now a bit more detail about the problem:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0xCFA21E00 0xA8838901 0x47CA6D03 0xXXXXXXX
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c6187426094d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x4 (0x4) flags: 0
Drücken Sie eine beliebige Taste . . .
Maybe you check this on your tablet as well.
HI all,
Sorry to hear that you have problem with your tab!!
happy to hear that you have exactly the same problem than me and others (see this http://forum.xda-developers.com/showthread.php?t=1790958)
I had made all possible test that i can
AFterota, Blackthun3er ,method, badsectros,fastboot, nvflash command......all failed to write the tab!!!!
gerardpuducul said:
HI all,
Sorry to hear that you have problem with your tab!!
happy to hear that you have exactly the same problem than me and others (see this http://forum.xda-developers.com/showthread.php?t=1790958)
I had made all possible test that i can
AFterota, Blackthun3er ,method, badsectros,fastboot, nvflash command......all failed to write the tab!!!!
Click to expand...
Click to collapse
Uhhh, that sounds not very good. At the moment I try EUU tool, but it seems also not working. So, did you give up on the tablet?
Hello!
I have rooted my phone today. i wanted to install some rom but first I tried to install TWRP so I can back it up. I tried a few different methods and tools, but nothing worked. Eventually I followed this tutorial: http://www.android.gs/install-twrp-recovery-lg-g2/ (I don't know if I'm allowed to posts links here...) about 5 times because everytime I forgot something. It still didn't work so I just give up. I re-booted my phone and I noticed some error in upper left corner, along with LG logo. But I still could boot it if I keep pressing power button. After that, some update showed up (I don't know which... :/) so i installed it and re-booted. And then there was error "secure booting error boot certification verify" and nothing works. I tried every combinations possible but I still cant boot it. The only thing that shows up is that error and LG logo and then it goes black (but it's still on). When I connect it to my PC it creates 12 empty 'local disk' and one 63,9 mb local disk (with folder 'image' and files in it). I tried this already: http://forum.xda-developers.com/showthread.php?t=2582142 using VirtualBox + Unbuntu but i'm stuck at the beginning. When I type "ls /dev/sd*" it only shows me the first " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 " and nothing else...
I'm seriously pissed off at me right now, last time I bricked my phone 2 years ago and I promised myself not to ever play with any of this stuff and now I got my new phone and screw it up next day. Yeah I got it for one day and I screwed it up already.
I'm freaking out, can someone please help me?
It might be you have sent the recovery Image to the wrong partition, in the mean time you will have to read what you have done, and maybe see if you selected something incorrectly, you may have to get another phone while you see if you can fix the broken one. I take it you have tried all boot options and no reset is available ?
I recently broke a working phone it is annoying, but you live and learn.
Sent from my Nexus 7 using XDA Free mobile app
prophice said:
Hello!
I have rooted my phone today. i wanted to install some rom but first I tried to install TWRP so I can back it up. I tried a few different methods and tools, but nothing worked. Eventually I followed this tutorial: http://www.android.gs/install-twrp-recovery-lg-g2/ (I don't know if I'm allowed to posts links here...) about 5 times because everytime I forgot something. It still didn't work so I just give up. I re-booted my phone and I noticed some error in upper left corner, along with LG logo. But I still could boot it if I keep pressing power button. After that, some update showed up (I don't know which... :/) so i installed it and re-booted. And then there was error "secure booting error boot certification verify" and nothing works. I tried every combinations possible but I still cant boot it. The only thing that shows up is that error and LG logo and then it goes black (but it's still on). When I connect it to my PC it creates 12 empty 'local disk' and one 63,9 mb local disk (with folder 'image' and files in it). I tried this already: http://forum.xda-developers.com/showthread.php?t=2582142 using VirtualBox + Unbuntu but i'm stuck at the beginning. When I type "ls /dev/sd*" it only shows me the first " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 " and nothing else...
I'm seriously pissed off at me right now, last time I bricked my phone 2 years ago and I promised myself not to ever play with any of this stuff and now I got my new phone and screw it up next day. Yeah I got it for one day and I screwed it up already.
I'm freaking out, can someone please help me?
Click to expand...
Click to collapse
Will your phone enter download mode? While it's fully powered down, hold the volume down and plug in a usb cable that's plugged into your pc. If you can get there, you're OK, there are options.
Sent from my LG-D800 using Tapatalk
After you do the dvb and it gives out 5 partitions, have you tried typing the name of the largest which would be 5 and seeing what happens
Sent from LG-G2 D800 on AEONFLEX 4.4.2
fatcarrotcake said:
It might be you have sent the recovery Image to the wrong partition, in the mean time you will have to read what you have done, and maybe see if you selected something incorrectly, you may have to get another phone while you see if you can fix the broken one. I take it you have tried all boot options and no reset is available ?
I recently broke a working phone it is annoying, but you live and learn.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
One thing that comes to my mind is that maybe the recovery image is not comptabilite with my phone. I know that when I tried to install TWRP with TWRP Manager it gave me an error when I chose g2d802 in device name so I didn't do it. The first link (tutorial I used) I posted, I used "openrecovery-twrp-2.7.0.0-d802" but I'm 99% it's the right one for my phone?
Jank4AU said:
Will your phone enter download mode? While it's fully powered down, hold the volume down and plug in a usb cable that's plugged into your pc. If you can get there, you're OK, there are options.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Unfortunately it doesn't enter download mode...
XxZombiePikachu said:
After you do the dvb and it gives out 5 partitions, have you tried typing the name of the largest which would be 5 and seeing what happens
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
You mean that "/dev/sda /dev/sda1 /dev/sda2 /dev/sda5" thing? I did that but it doesn't do nothing.
PLEASE can someone else reply? I seriously don't know what to do.
prophice said:
PLEASE can someone else reply? I seriously don't know what to do.
Click to expand...
Click to collapse
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
prophice said:
The only thing that shows up is that error and LG logo and then it goes black (but it's still on).
Click to expand...
Click to collapse
At that point, press and hold the power button for 30 seconds to make sure its off completely. Then try download mode again. If you've already been doing that, disregard.
bender_007 said:
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
Click to expand...
Click to collapse
I used that tutorial and Im in ubuntu atm, but i dont think it is detecting my lg at all. When using -ls /dev/sd*- its now showing -/dev/sda /dev/sda1 /dev/sda2 /dev/sdb /dev/sdb1- And when using -gdisk -l /dev/sdb- it gives me
[email protected]:~$ sudo gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 15630336 sectors, 7.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AB4CD8FE-B964-4DCD-8AF2-43C5051BC71D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15630302
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 15630335 7.5 GiB 0700 Microsoft basic data
Click to expand...
Click to collapse
and
[email protected]:~$ sudo gdisk -l /dev/sdb1
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Exact type match not found for type code F400; assigning type code for
'Linux filesystem'
Exact type match not found for type code 1000; assigning type code for
'Linux filesystem'
Exact type match not found for type code 7400; assigning type code for
'Linux filesystem'
Warning! Secondary partition table overlaps the last partition by
3454418421 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb1: 15628288 sectors, 7.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): A3BCA950-18FB-4E37-9B41-0F662D454416
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15628254
Partitions will be aligned on 1-sector boundaries
Total free space is 15628221 sectors (7.5 GiB)
Number Start (sector) End (sector) Size Code Name
1 3223366752 3470046675 117.6 GiB 8300 Linux filesystem
2 378192737 710426324 158.4 GiB 8300 Linux filesystem
3 225603442 225603451 5.0 KiB 8300 Linux filesystem
Click to expand...
Click to collapse
And also now when conected lg the ecran is flashing between black and very black,
And I used the lines you gave me obviously but I dont think it did anything,
Any messages popping up?
Sent from my LG-D802 using XDA Premium 4 mobile app
Nope, nothing.
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =) Now that I'm in TWRP i'd like to install a rom, Am I safe to do it? I was thinking about Pardus HD but I have 2 questions.
1. I'm in TWRP but the computer doesn't detect my phone, how i am supposed to copy PardusHDC_7.1.zip to my phone?
2. it says "Upgrade your Recovery to TWRP 2.7.0.0 or Latest Philz Recovery" in installation guide, I have v2.6.3.2, will that make any difference?
Adb push pardushdc...zip /sdcard/pardus.zip
Sent from my LG-D802 using XDA Premium 4 mobile app
Ok I got it but before I start installing Id still like to know if im safe to do it with my current TWRP version?
prophice said:
Ok I got it but before I start installing Id still like to know if im safe to do it with my current TWRP version?
Click to expand...
Click to collapse
I think you need to update recovery or else install will just fail because of outdated files
Sent from LG-G2 D800 on AEONFLEX 4.4.2
It didn't work on v2.6.3.2 but it did on v2.7 and oh god I flashed that rom and it works!!!!! This is awesome, I don't know how I can thank you for all that help!!
please now make a backup and put it somewhere ie pc,usb stick,meenova safe, im glad you got it sorted and i know exactly how you felt as ive been in that situation a few times!!
prophice said:
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =)
Click to expand...
Click to collapse
How do you make it? Please, I am stuck on this.
Please help dude....
prophice said:
OK it works!!!! I guess all I had to do is get some sleep and think fresh. =) Now that I'm in TWRP i'd like to install a rom, Am I safe to do it? I was thinking about Pardus HD but I have 2 questions.
1. I'm in TWRP but the computer doesn't detect my phone, how i am supposed to copy PardusHDC_7.1.zip to my phone?
2. it says "Upgrade your Recovery to TWRP 2.7.0.0 or Latest Philz Recovery" in installation guide, I have v2.6.3.2, will that make any difference?
Click to expand...
Click to collapse
Hi, I am facing the exact same issue as you described. I am using a LG G2 D802 international version. I did everything I could find on the internet. Could you please help me by telling how you got it working?? I am using a bootable USB of ubuntu and lsusb is showing my phone as Qualcomm 9006 but when I type ls /dev/sd* it is not giving me the device due to which I could not push the partition files. Please dude help me it has been 5 days since I am trying. You can PM me on my email [email protected]
Thanks in advance
---------- Post added at 11:07 AM ---------- Previous post was at 10:57 AM ----------
bender_007 said:
Try this method
Then boot from the usb stick(don't install ubuntu..just boot)
open terminal
copy and paste this - line by line (enter)
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount False
gconftool-2 --type bool --set /apps/nautilus/preferences/media_automount_open False
Then follow the instructions
Click to expand...
Click to collapse
Hi,
I saw your reply on the post which is related to the same issue I am facing since last 5 sleepless nights . I have a LG G2 D802 international variant and it had kitkat 4.4.2 earlier which I have successfully rooted. I recently received an OTA which I clicked to update [worst day of my life ] after that my phone is stuck in boot loop and rest you know. I trying to use ubuntu to push the partition files and recovery, but my phone is not detectable in ubuntu. lsusb is showing my phone as Qualcomm 9006 but when I type ls /dev/sd* it is not showing my phone. I saw your method in the quote and tried this also but it is still not working . Could you please let me know how can I solve this? Also by using the commands above does the phone needs to be connected or not ?? Please help me . You can PM me on [email protected].
Thanks is advance
Hello, i suggest to download vmware and slax ISO and run slax inside vmware. Then try the instructions. I can assist you but on monday , sorry
Poslano sa mog LG-D855 koristeći Tapatalk
Hey guys, I was trying to increase app storage by re-partitioning the internal storage with Mt657xRepartition_EN.apk, where I selected 1gb for app storage. The next step was to wipe data/factory reset. Post this step, the phone is stuck at boot logo. So I tried restoring my backup via CWM and it failed while restoring /system. The log reveals that system cannot be restored due to no space left on the partition. As per my understanding, the above repartitioning was for data partition, but it may have messed up something. Here is full log while trying to restore system from advanced restore:
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created file system with 11/32768 inodes and 4206/131072 blocks
SDCardUpdate.apksdcarda7d2cf64.0bouncycastle.odexlibbinder.solimobilelog_jni.soProcyon.oggOrganDub.oggtar: write error: No space left on device Vendor_045e_Product_028e.klError while restoring /system!
When connected to MTKDroidTools, the device is recognised in CWM recovery, but the kernel and baseband fields are empty. There is a blue dot at bottom left with some Russian word (see attachment). With MTKDroidTools, I was able to recover block map on the ROM (see attachment) where it says the following: System space is 64,27,77,088 bytes. The recovery on the PC says the system.ext4.tar file is 52,72,86,272 bytes. Therefore it should be able to restore, right? Also, isn't cache a bit too big at 485490688 bytes, which is same as usrdata at 463mb? usrdata was about 463mb before starting this, so that means partitioning failed, right? (I had selected 1 gb for the same).
My apologies that I do not have the original block map of the phone, but the usrdata (apps) and fat (media) seem to be the same. Should I try wiping system and restoring again via CWM?
Other Details:
Note: 1. I am able to restore /data and /cache from CWM recovery. I'm a bit worried to try restoring boot partition
2. Backup was made using Custom CWM recovery made with MTKDroidTools
Device: ZTE Blade C
Processor: MT6577 by Mediatek
Storage: 4gb (about 430 to 460mb was internal storage (apps) and 2.2gb was phone storage (media))
ROM: Official, was rooted with vroot and replaced by SuperSU.
I tried flashing custom rom via spflashtools, but it seems to stay stuck at 0% with word searching below (It does recognize that connected at start). Probably has to do with the fact that the phone cannot connect properly to PC when connected in preloader mode (I have installed preload drivers, but the phones seems to connect and disconnect every second)
I really need to revive this device, preferably with some extra space in usrdata partition, if possible. I have browsed several threads and collected this information based on that. Any pointers, help, information, diagnosis, guidance, steps, etc. would be much appreciated. I'll try my best to find my way to the solution. Please tell me if you need any other info. This device is at the edge of bricking. And I had given this to my dad on Father's Day 2 days back. He wasn't receiving emails due to low storage and I told him I can fix it. It would be terrible if I tell him I killed his phone.
Thanks for consideration to those who read through and did not reply for being unable to help.
Update:
When backup was made with MTKDroidTools, I found this:
- nodl_pmt
- PMT tables found
- PMT tables OK, 18 blocks found
--- Kernel Block Map to PMT mismatch!
-------------------------------------------
BlockName Offset
-------------------------------------------
Kernel: __NODL_BMTPOOL 0x00000000FFFF00A8
PMT: Not present! ??????????
-------------------------------------------
--- scatter from PMTis write to the file:
E:\Desktop\Android\MTKDroid\backups\ZTE-BLADE-C_130508_backup_140617-053203\MT6577_Android_scatter_emmc_PMT.txt
- Use it if SP FlashTool errors of 8038 or 4050 occurs
Hi!
Unfortunately playing with partitions can be a sensitive affair. Best left for very experienced tinkerers. Best way to free up space, is to free up space.
I hesitate to point you to any one particular thread, as I am not sure with your device exactly where you stand....and what you can and can't do at this point.
I will ask a moderator to move your thread to the Blade section, so you don't have to type all this out again. One thing, maybe put your device info at the very top of your thread and even edit your thread title to say Blade C. That will get you more model specific help hopefully.
Your thread will be moved here, to ZTE Blade General section....
http://forum.xda-developers.com/zte-blade/general?nocache=1&z=6848981278017163
Good luck! ?
Can the post please stay here for a little while? :fingers-crossed: As you said, this stuff is for experienced Android tinkerers and I believe there will be many more experienced folks here than in the ZTE blade forum.
With the update, I think I am closing in on the problem. I just need to understand how I can fix "Kernel Block Map to PMT mismatch". I have also requested folks with ZTE blade C to retrieve the original partition tables via MTKDroidTools.
Thanks for your time.
msmsmsmsms said:
Can the post please stay here for a little while? :fingers-crossed: As you said, this stuff is for experienced Android tinkerers and I believe there will be many more experienced folks here than in the ZTE blade forum.
With the update, I think I am closing in on the problem. I just need to understand how I can fix "Kernel Block Map to PMT mismatch". I have also requested folks with ZTE blade C to retrieve the original partition tables via MTKDroidTools.
Thanks for your time.
Click to expand...
Click to collapse
Sorry. XDA Assist is a place to get shown the way, not for troubleshooting or discussion. If you want answers, the area for your device is definitely the best place to post.
Please delete this thread. I had requested a mod 2 days back, but haven't received a reply.