I managed to hard-bricked my Nexus 6P and now my phone won't turn on at all. I already tried everything to make sure it's not a soft-brick so that doesn't have to be asked.
I found this article: wwwDOTdroidsavvyDOTcom/unbrick-qualcomm-mobiles/ (unfortunately I can't post links so please replace the DOT with .) stating that I can unbrick it by using some tools. Unfortunately I need a full eMMc backup from someone with a factory-resetted Nexus 6p.
I wanted to ask if someone can do this huge favor and upload a backup of their eMMc somewhere. I would be very thankful for that!
To do so, it has to be a rooted factory-resetted Nexus 6P (although you can try without a factory-reset). These commands have to be entered:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/emulated/0/backup.img bs=512 count=30535646
and then the file has to be uploaded somewhere.
I would very appreciate it if someone does this or suggests something different. Thanks in advance!
i could really do with the same, this would be really handy. Phone all bricked up
Any luck with this? Mine ricked yesterday sounds the me.... Wont turn on, doesnt react to charger or plugging in to laptop
Sent from my LG-D802 using XDA-Developers mobile app
Custom Recovery OK?
The only problem I'm forseeing is that my unique data in my EFS partition may then be public - like my IMEI, Serial Number, etc.
How can you confirm such data won't be in this factory image?
You can wipe your efs partition and it will restore itself properly. You don't need a backup. If you can't get to fastboot/recovery then you won't be able to do this.
brickedsmh said:
I managed to hard-bricked my Nexus 6P and now my phone won't turn on at all. I already tried everything to make sure it's not a soft-brick so that doesn't have to be asked.
I found this article: wwwDOTdroidsavvyDOTcom/unbrick-qualcomm-mobiles/ (unfortunately I can't post links so please replace the DOT with .) stating that I can unbrick it by using some tools. Unfortunately I need a full eMMc backup from someone with a factory-resetted Nexus 6p.
I wanted to ask if someone can do this huge favor and upload a backup of their eMMc somewhere. I would be very thankful for that!
To do so, it has to be a rooted factory-resetted Nexus 6P (although you can try without a factory-reset). These commands have to be entered:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/emulated/0/backup.img bs=512 count=30535646
and then the file has to be uploaded somewhere.
I would very appreciate it if someone does this or suggests something different. Thanks in advance!
Click to expand...
Click to collapse
May I know how you hard bricked it? Just curious is all...
Sent from my LG G4 using Tapatalk
I tried to do a full backup twice now with that command. Corrupt both times. Doesn't help that it takes about 12gb of storage.
I'm running command now. it will probably take a bit. will keep you posted.
How do you know your backups were corrupted? I only ask because if I manage to upload the file I wouldn't want to upload a corrupt file to anyone.
Edit:2 I managed to get file. Its over 14GB, i didnt wipe phone before hand. Im going to upload to mega.
Fe Mike said:
I'm running command now. it will probably take a bit. will keep you posted.
How do you know your backups were corrupted? I only ask because if I manage to upload the file I wouldn't want to upload a corrupt file to anyone.
Edit:2 I managed to get file. Its over 14GB, i didnt wipe phone before hand. Im going to upload to mega.
Click to expand...
Click to collapse
I tried to mount them to see what was inside. Mine were probably corrupt because I didn't have enough storage space to make the whole img. Did you have storage space left over after this?
tr4nqui1i7y said:
I tried to mount them to see what was inside. Mine were probably corrupt because I didn't have enough storage space to make the whole img. Did you have storage space left over after this?
Click to expand...
Click to collapse
Yes but not much. I didn't try mounting it. And it took forever for both creating file and uploading it. But here is the uploaded backup. I hope it works for those with bricked devices.
https://mega.nz/#!sZBEiRIR!z4CjoF1m0a47ZyLtKkXXkKMUtaxe7yLUV577LHQ7dmo
Fe Mike said:
Yes but not much. I didn't try mounting it. And it took forever for both creating file and uploading it. But here is the uploaded backup. I hope it works for those with bricked devices.
https://mega.nz/#!sZBEiRIR!z4CjoF1m0a47ZyLtKkXXkKMUtaxe7yLUV577LHQ7dmo
Click to expand...
Click to collapse
That's from a fresh install, right? Just want to make sure you don't share anything private
tr4nqui1i7y said:
That's from a fresh install, right? Just want to make sure you don't share anything private
Click to expand...
Click to collapse
I did do a wipe and reflashed factory images the second time but did turn on device to install supersu app before I realized I could just do it through adb shell because I did flash supersu. So there is a google account linked to it. I changed my password so not sure if that will be an issue. I'm assuming as soon as your up and running you'll wipe and restore your stuff. I didn't wipe the efs though. My backup was on MTC20F and recovery twrp-3-0-2.2.
Fe Mike said:
I did do a wipe and reflashed factory images the second time but did turn on device to install supersu app before I realized I could just do it through adb shell because I did flash supersu. So there is a google account linked to it. I changed my password so not sure if that will be an issue. I'm assuming as soon as your up and running you'll wipe and restore your stuff. I didn't wipe the efs though. My backup was on MTC20F and recovery twrp-3-0-2.2.
Click to expand...
Click to collapse
Just to clarify, your password is now different than the one in the backup? Just making sure. Don't want you leaking your data! Thanks again for the backup.
tr4nqui1i7y said:
Just to clarify, your password is now different than the one in the backup? Just making sure. Don't want you leaking your data! Thanks again for the backup.
Click to expand...
Click to collapse
Yes it's different now.
Fe Mike said:
Yes it's different now.
Click to expand...
Click to collapse
Perfect! You rock. If we can get this figured out, then our device could potentially become unbrickable!
tr4nqui1i7y said:
Perfect! You rock. If we can get this figured out, then our device could potentially become unbrickable!
Click to expand...
Click to collapse
it's crazy how many Nexus phones are bricked. just in the general forum alone. this is my first Nexus and thought they couldn't brick unless you really tried. Did yours brick with that whole twrp-3-0-2.1 and nougat fiasco?
While the article that the OP mentioned has the general idea, anyone attempting this should verify the partition structure of the Nexus 6P against what the scripts are doing:
https://gist.github.com/zhuowei/79b6fbcd9ba9f1726163
Just an FYI. Also compressing the backup should make a huge difference in file size, if another upload is done in the future.
Also, the contents of /persist will be restored with such a backup... for more details see:
http://forum.xda-developers.com/nexus-6p/help/formatted-nexus-6p-persist-partition-t3453035
There are at least 2 things unique to each phone in that partition:
1) sensor calibration file (which I describe how re-create in the post above)
2) speaker calibration file (which would be tricky to adjust perfectly, except by a trial and error process)
vacaloca said:
While the article that the OP mentioned has the general idea, anyone attempting this should verify the partition structure of the Nexus 6P against what the scripts are doing:
https://gist.github.com/zhuowei/79b6fbcd9ba9f1726163
Just an FYI. Also compressing the backup should make a huge difference in file size, if another upload is done in the future.
Also, the contents of /persist will be restored with such a backup... for more details see:
http://forum.xda-developers.com/nexus-6p/help/formatted-nexus-6p-persist-partition-t3453035
There are at least 2 things unique to each phone in that partition:
1) sensor calibration file (which I describe how re-create in the post above)
2) speaker calibration file (which would be tricky to adjust perfectly, except by a trial and error process)
Click to expand...
Click to collapse
Thanks for the info!
Check in on progress in this thread - here
The goal is to get a raw operator rom for our device. That would include nothing other than necessary boot info for our devices.
You'd still have to flash-all the fastboot files to boot.
This is just to get corrupt eMMC back on track.
In the process of making our own programmer file using our partition information.
Bricked 6p
I have accindently wiped internal data from twrp hence it shows says "no os installed" do you want to restart ?
I tried flasing cm13 n benzo rom zips frm twrp didnt work then..
I tried nexus toolkit unbrick+backtostock process was done flawlessly still didnt go beyond google logo(kept my phone in bootloop for all night)
then I tried flasing offical factory image still didint work..m nt understanding the hell is going wrong
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
tr4nqui1i7y said:
That's from a fresh install, right? Just want to make sure you don't share anything private
Click to expand...
Click to collapse
why file size is to big
atharva1997 said:
I have accindently wiped internal data from twrp hence it shows says "no os installed" do you want to restart ?
I tried flasing cm13 n benzo rom zips frm twrp didnt work then..
I tried nexus toolkit unbrick+backtostock process was done flawlessly still didnt go beyond google logo(kept my phone in bootloop for all night)
then I tried flasing offical factory image still didint work..m nt understanding the hell is going wrong
---------- Post added at 07:51 PM ---------- Previous post was at 07:48 PM ----------
why file size is to big
Click to expand...
Click to collapse
That backup is for something way different.
Related
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
fykick said:
I know you guys hate when people jump the gun...but I'm honestly running out of ideas here. Earlier today I tried to use LCD Density changer on my Nexus S...whether this was stupid on my part, you all can decide later. As for now my nexus boots a black screen. I'm only posting here cuz maybe in finding a solution we can uncover a bit about how the nexus is set up, because it seems to refuse any changes made to the system through fastboot or adb push.
I have tried just about every option to restore the system to stock format, and need help getting my nexus back to booting condition. I've tried fastboot flashing the system.img and just get a "write failed" error. I've pushed the whole system dump to /system through adb and when i reboot it is still missing the files i just pushed. I've flashed different boot.img's in combination with the first two steps, and still my phone remains unbootable.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
Is it safe to say you didnt do nandroid restore prior?
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
fykick said:
Yes, that is correct...didn't think it'd cause this much of a problem(stupid me). I asked earlier if maybe some could upload a nandroid restore for me so I could at least attempt that. But I got no response, so I'm still in the dark.
Click to expand...
Click to collapse
When I get home in an hour, I'll factory wipe and make a backup of the stock rom for you.
Any recommendations on where to upload?
I got you man im backing up right ow....going to wipe then backup again and ill upload it so give me a bit
maybe ill be really nice and include some custom transitions for you
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
nandroid
pm'ing you the link
let me know if it works
mount usb storage copy and paste the into clockworkmod/backups
unmount usb storage and restore....gave you all the goodies too
nxt said:
Only been 1 day since it came out, since it boots to black, take it back to the store, act stupid, get another one. Solved.
Click to expand...
Click to collapse
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
Click to expand...
Click to collapse
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
wdfowty said:
Hahahahaha best thing I've heard all day
Apparently the NS is super-brickable, according to JBQ (@jbqueru) on android-building:
Click to expand...
Click to collapse
Now that is a frightening prospect;( How can google make a dev phone thats super brickable... hmmm
JD
AndHel said:
Is there anyway I can get the link for that nandroid? I seem to have messed my system files up as well.
Click to expand...
Click to collapse
Can I get the link for the stock nandroid also? I need to use a secure boot image.
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
OKay
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
drexman8244 said:
So i sent the backup to at least 3 people anyone care to let me know hows its going and whether or not they like the customizations
Click to expand...
Click to collapse
maybe you can upload it to mediafire or somewhere else, and create a thread? it might help others out
ill take your advice on that Thanks
adb push may not have been working because your system wasn't mounted properly in Clockwork recovery. I had this issue when trying to root. In Recovery, go to Mounts & Storage and hit "Mount System" THEN adb push the system dump.
You probably didn't need to nandroid. Could have just used adb to reset the density line in your build.prop I assume?
fykick said:
Okay, thank you very much for the Nandroid. It worked and I'm back up and running.
Click to expand...
Click to collapse
Please mention it on the Thread Title PROBLEM SOLVED.
An nandroid backup can be found here http://forum.xda-developers.com/showthread.php?t=877601
Hi guys, i'm the developer of LCD Density Changer. Sorry about the problems it caused.
Is it true that the Nexus S, doesn't support a density change. That would be a real bummer! Not for the app, but in general. I just don't hope Google blocks a density change in their new Android versions.
A question: does the "preview/temporarily" density change works in the LCD Density Changer app. If so, there is still hope.
Meanwhile, based on these reports I will put up a note to warn Nexus S users.
Just wondering if anyone who's flashing and rooting could please do a backup and upload it somewhere. Myself and a couple others have accidentally partitioned our internal SD incorrectly causing a catastrophic touch screen issue.
I'm hoping it'll have the properly partitioned SD storage because I'm having difficulty doing it manually. If someone could upload this it'd be hugely appreciated!!!
BUMP!!!
Can anyone please provide me with a Nandroid backup using Tenfar's recovery??? I can throw some money once I get my Paypal sorted out. I'm desperate, fellas!
Can someone please help? I'd like to try anything I can to get my phone working this weekend. It's been an entire week without my Atrix.
bongd said:
Can someone please help? I'd like to try anything I can to get my phone working this weekend. It's been an entire week without my Atrix.
Click to expand...
Click to collapse
Im relatively new to android...is this backup you are speaking about a TB backup. Or what method of backup are you looking for?
Sent from my MB860 using Tapatalk
You actually need to be rooted and have Tenfar's custom Recovery menu. In there it has an option to do a Backup.
If you're new it may be too engaging but I appreciate the offer nonetheless. If you could help, it'd be great. If it's too much trouble, I thank you anyway!
yeah what does the nandroid backup...back.. up? the apps?
What I'm HOPING and PRAYING for is that it'll also copy something in the internal SD which was partitioned due to my stupidity. dev/block/mmcblk0p18 is what that is in particular.
I tried manually formatting and partitioning it but I'm unable to do so. Fastboot freezes and Early USB Enumeration goes by so quickly I can't run the commands that I need through ADB. And I don't even know if that'll work because I made a script that executes the commands and I get weird errors. I'm far from an expert and monkeyed around too deeply where I shouldn't have.
About 4-5 others are reporting the same problem. The ****ty thing is that I'm in Canada and it'd be a huge pain to send it to Motorola. They're giving me a lot of grief and I've had to put up a big fight. Waiting to see if they'll send an RMA because I may need to send it in. When I get it back I might sell it and buy a Bell Atrix because I live in Canada and if something bad happens, it'll be easier to send to Bell or Motorola Canada.
from what i understand you have to have an unlocked bootloader to backup or restore using a nandroid backub
Maybe I'm using the wrong terminology then.. just need a backup from Tenfar's customer Recovery. I don't even know if it'll work but I'm out of ideas.
I'm at least thankful that the Xperia X10's bootloader was cracked. I forgot to send a replacement back to Rogers and I phoned them asking if I could use it for now. They thankfully said yes because they forgot to charge me for it lol... it's got some really great ROMs, but looking at this beautiful, mangled Atrix makes baby Jesus cry!
i can do that but im wondering why you dont try SBF file?? should work better than Backup
zen kun said:
i can do that but im wondering why you dont try SBF file?? should work better than Backup
Click to expand...
Click to collapse
i was just wondering the same thing... it also be more stable as nandroid restore are not so good on some phones and im guessing especially on a locked bootloader one.
also a nandroid backup would also restore some else's settings and information on your device....
Ronaldo_9 said:
i was just wondering the same thing... it also be more stable as nandroid restore are not so good on some phones and im guessing especially on a locked bootloader one.
also a nandroid backup would also restore some else's settings and information on your device....
Click to expand...
Click to collapse
I've already tried the SBF files but it doesn't do anything to the internal SD. I need an actual backup because the user settings are exactly what I'm looking for. Normally you'd want a fresh flash from stock but I hope you now understand why I'm asking this constantly.
Flashing to stock was naturally my first step. Unfortunately it had failed. About 5 others reporting the same problem.
bongd said:
I've already tried the SBF files but it doesn't do anything to the internal SD. I need an actual backup because the user settings are exactly what I'm looking for. Normally you'd want a fresh flash from stock but I hope you now understand why I'm asking this constantly.
Flashing to stock was naturally my first step. Unfortunately it had failed. About 5 others reporting the same problem.
Click to expand...
Click to collapse
What maybe you could do is? go into tenfars cwm recovery go to mounts and storage and format the internal sdcard and system and boot and data. This is safe as far as I know and me and tenfar have both done this.I literally formatted every single thing in the option menu. just to see if I could do it. Which was stupid but I was curious and used to do that before I installed new roms on my old backflip all the time! Also might wanna do a factory reset through cwm and clear dalvik cahe as well for good measure. Now after you format all that. reboot system which will send you in a boot loop/wont boot past first screen. Pull the battery and unplug usb cable from charger. Then reboot and enter rsdlite mode by holding volume up and the power button. Now just flash your 4.1.26 sbf file through rsdlite 5.0
As long as you flash back to retail 4.1.26 afterwords using rsdlite 5.0 that should put everything right! As I have done this and my phone is working normal.
I better put one of them warnings here though anyway lol
Disclaimer: You are doing this at your own risk! I am not responsible for any damage you do to your phone.
(^Yeah I think that covers it)
Gutterball said:
What maybe you could do is? go into tenfars cwm recovery go to mounts and storage and format the internal sdcard and system and boot and data. This is safe as far as I know and me and tenfar have both done this.I literally formatted every single thing in the option menu. just to see if I could do it. Which was stupid but I was curious and used to do that before I installed new roms on my old backflip all the time! Also might wanna do a factory reset through cwm and clear dalvik cahe as well for good measure. Now after you format all that. reboot system which will send you in a boot loop/wont boot past first screen. Pull the battery and unplug usb cable from charger. Then reboot and enter rsdlite mode by holding volume up and the power button. Now just flash your 4.1.26 sbf file through rsdlite 5.0
As long as you flash back to retail 4.1.26 afterwords using rsdlite 5.0 that should put everything right! As I have done this and my phone is working normal.
I better put one of them warnings here though anyway lol
Disclaimer: You are doing this at your own risk! I am not responsible for any damage you do to your phone.
(^Yeah I think that covers it)
Click to expand...
Click to collapse
JUST got your PM as I was clicking this thread. Thanks, broski.
I've got nothing to lose. It's easy enough to recover from soft-brick. I'll give it a shot right now. Wish me luck!
*** UPDATE ***
Still no dice. Bummer.
bongd said:
JUST got your PM as I was clicking this thread. Thanks, broski.
I've got nothing to lose. It's easy enough to recover from soft-brick. I'll give it a shot right now. Wish me luck!
*** UPDATE ***
Still no dice. Bummer.
Click to expand...
Click to collapse
mmm weird..
IMO if sbf dont help i really doubt a recovery will....
perhaps i highly recommend if someone do this, create a new account of gmail and flash a sbf file since the OP will have all sensitive data as email,contacts and so on as previous post say
zen kun said:
mmm weird..
IMO if sbf dont help i really doubt a recovery will....
perhaps i highly recommend if someone do this, create a new account of gmail and flash a sbf file since the OP will have all sensitive data as email,contacts and so on as previous post say
Click to expand...
Click to collapse
That won't work either. I have reasons for wanting a backup versus a new SBF flash as stated multiple times.
I have a nand if you still need one
Sent from my MB860 using XDA App
sgtmedeiros said:
I have a nand if you still need one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Your motoblur account information is stored in plaintext and your google contact information is also in a nandroid backup. Be weary.
knigitz said:
Your motoblur account information is stored in plaintext and your google contact information is also in a nandroid backup. Be weary.
Click to expand...
Click to collapse
I was not aware of this and was so focused on correcting the challenge that this was a complete oversight. On second thought, I don't want to compromise anyone's security.
I had in mind a fresh backup, preferably for AT&T's 1.2.6 SBF but it's a bit of trouble and a lot of space. I retract my request due to the amount of work involved and that I don't want to compromise anyone's security in case they don't clear their user details, etc.
Thanks for pointing that out, knigitz. I think ADB access in the Recovery is our best bet. Crossing my fingers.
bongd said:
You actually need to be rooted and have Tenfar's custom Recovery menu. In there it has an option to do a Backup.
If you're new it may be too engaging but I appreciate the offer nonetheless. If you could help, it'd be great. If it's too much trouble, I thank you anyway!
Click to expand...
Click to collapse
Ill help you with your backup if you can help me root and flash the gladix rom on mine.
Sent from my MB860 using XDA App
Does anyone happen to have a nandroid backup for ThinkPadTablet_A310_02_0037_0075_US?
I'm confused - your thread title requests a different backup than the message.
I may have the 0075 in my backups, I'll look and see.
Wow just noticed that I did that. I'm looking for the 0075 nandroid backup. MANY thanks in advance if you happen to have one.
dwilli40 said:
Wow just noticed that I did that. I'm looking for the 0075 nandroid backup. MANY thanks in advance if you happen to have one.
Click to expand...
Click to collapse
I have one but there are issues with the build.prop plus some personal info in there
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Clean, fresh and rooted nandroid image of 0075
Dwilli40,
Factory reset 0075 US rooted Nandroid -- built it for you last night.
No-Bloat: http://www.diginous.com/no_bloat_0075_US_root_NANDROID.zip
Extract to SD-card, use CWR to restore.
From a 32gb TPT. Cheers!
pwstein said:
Dwilli40,
Factory reset 0075 US rooted Android -- built it for you last night.
Couldn't upload to everyrandom.com from the tablet so it is here:
http://aksenate.org/clean_0075_US_root_NANDROID.zip 550mb, extract to SD-card, use CWR to restore.
From a 32gb TPT. Cheers!
Click to expand...
Click to collapse
Hell if this don't help him it definitely helps me thank u
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
cool ker2gsr! Happy to help. I was thinking about building another nandroid of 0075 without Lenovo bloatware. I'm guessing both types of backups might be useful in the long run.
Dwilli40 - could you edit the thread title to reflect your request for 0075? It may help others to find a solution if they are in similar straights.
pwstein said:
cool ker2gsr! Happy to help. I was thinking about building another nandroid of 0075 without Lenovo bloatware. I'm guessing both types of backups might be useful in the long run.
Dwilli40 - could you edit the thread title to reflect your request for 0075? It may help others to find a solution if they are in similar straights.
Click to expand...
Click to collapse
All I needed was a build.prop lol but its good to have just in case since there is no actual system .img out there
Sent from my Galaxy Nexus using Tapatalk
Thank you very much pwstein. I have edit the title as you guys requested.
Just what I'm looking for!
pwstein said:
Dwilli40,
Factory reset 0075 US rooted Nandroid -- built it for you last night.
Couldn't upload to everyrandom.com from the tablet so it is here:
http://aksenate.org/clean_0075_US_root_NANDROID.zip 550mb, extract to SD-card, use CWR to restore.
From a 32gb TPT. Cheers!
Click to expand...
Click to collapse
pwstein,
Thank you so much for this Nandroid backup!
This is exactly what I need to get my TPT back to being able to run encryption.
My current ROM has been updated to 0089_US.
Are there any issues I should be aware of in using this Nandroid backup to roll back to 0075?
Please advise me accordingly.
Thanks!
Konker
Konker,
No issues to speak of. It is a factory reset, booted through startup without wifi, no account info provided, Lenovo standard bloatware, and no customization. SuperUser is already installed and active. The backup folder was renamed and then added to a zip file.
My tablet has a Gobi3000 wwan card installed, otherwise a standard 1838 with 32gb storage.
I hope it helps anyone who didn't get a backup made before upgrading.
Unzip file to sd-card /clockworkmod/backup/
Put sd-card in tablet
Shut down, boot to CWR, (make your own backup), restore to 0075
Enjoy
I keep getting a MD5 checksum error. I have tried to re-downloading several times but still getting the error. Any ideas on how to fix this?
Try from the uploads I put on everyrandom.com today. The previously linked one was uploaded (550MB) on 3G cell service, likely screwing it up somehow.
edit: everyrandom.com/files wasn't serving the files correctly. They have been removed.
See thread: http://forum.xda-developers.com/showthread.php?t=1566508
dwilli40 said:
I keep getting a MD5 checksum error. I have tried to re-downloading several times but still getting the error. Any ideas on how to fix this?
Click to expand...
Click to collapse
I was also so I installed the second CWM version about half way through that thread, and the restore went smooth.
Whoa, I just realized I never installed the improved CWR port. Mine is the original CWR that was offered up on the first day of Root. I should remember that because I ALWAYS pull my SD-Card out before performing factory resets. I heard the CWR update fixed that...
I'll note that in my Nandroid post. Thanks for the heads up.
I figured out what was going on. I guess when I extracted the files, it put the files in a sub folder with the name as the original folder.
I tried to download from the other post also, but it was like the files had been removed from the site.
rangercaptain said:
I was also so I installed the second CWM version about half way through that thread, and the restore went smooth.
Click to expand...
Click to collapse
Where can I find the supposed updated CWM port? I cannot find it in this thread nor anywhere related to the TPT.
Please advise me.
Thanks!
I fixed it to a direct download link for the no bloat nandroid.
0075 US clean, rooted Nandroid
konker said:
Where can I find the supposed updated CWM port? I cannot find it in this thread nor anywhere related to the TPT.
Please advise me.
Thanks!
Click to expand...
Click to collapse
See this post
Device specific files. Same instrutions as in the OP.
rangercaptain said:
See this post
Device specific files. Same instrutions as in the OP.
Click to expand...
Click to collapse
Thanks for the link!
I updated the CWM on my TPT with this version & I discovered that the recovery console is not as stable.
No long after I reboot into CWM recovery, perhaps about 10 secs, my TPT rebooted itself.
Has anyone observed this behavior?
I'm going to try download again & see how it goes.
Konker
I'd appreciate help porting CWM and Cyanogenmod! Please post, fork, request merges etc...
I've managed to compile CWM for the Lenovo Yoga 10 HD+
My repository is here: https://github.com/zyrill/android_device_lenovo_b8080h
And the CWM recovery image is attached. Use towelroot by geohot to root your tablet.
Before attempting to flash, you should:
make sure you know what you're doing!
double check that you're flashing the right partition!
If you flash the wrong partition, you'll brick your tablet!
You can check your partition layout with
Code:
$ ls -al /dev/block/platform/msm_sdcc.1/by-name/
Once rooted, you can flash the image as follows:
Code:
$ adb push recovery.img /storage/sdcard0/recovery.img
$ adb shell
$ dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p21
Enjoy!
Changelog:
v 0.1: Initial version. Known issue: can't yet mount /sdcard and external cards
v 0.2: Backup is operative! Known issues: no option to backup to external storage, no option to skip backing up of external storage, date is not set correctly
zyrill said:
I'd appreciate help porting CWM and Cyanogenmod! Please post, fork, request merges etc...
I've managed to compile CWM for the Lenovo Yoga 10 HD+
Click to expand...
Click to collapse
Very nice @zyrill!!!! :good:
Thank you so much!
Did anyone tested it yet?
Regards,
Asmaron
asmaron said:
Very nice @zyrill!!!! :good:
Thank you so much!
Did anyone tested it yet?
Regards,
Asmaron
Click to expand...
Click to collapse
Yep! I´ve done! TowelRoot works.
And It works fast and without problems. I have used the tr.apk with date 04.07.2014 and done on the
B8080 with Firmware B8080_S102202_140716_ROW_3GData
Needs 2-3 Seconds and now I have root! But don´t forget to install SuperSu!
Bringer1 said:
Yep! I´ve done!
And It works fast and without problems. I have used the tr.apk with date 04.07.2014 and done on the
B8080 with Firmware B8080_S102202_140716_ROW_3GData
Needs 2-3 Seconds and now I have root!
Click to expand...
Click to collapse
Thanks! I'll give it a try later on!
asmaron said:
Thanks! I'll give it a try later on!
Click to expand...
Click to collapse
Well don't worry, I've got it running on my tablet for all that time now and of course it works, else I wouldn't have posted it. If I find some more time, I'll start porting CM as well, but that might be a while, I'm a bit busy right now.
Most Excellent
zyrill said:
Well don't worry, I've got it running on my tablet for all that time now and of course it works, else I wouldn't have posted it. If I find some more time, I'll start porting CM as well, but that might be a while, I'm a bit busy right now.
Click to expand...
Click to collapse
I installed this and it seems to be working. I backed up my current configuration but have not yet tried to restore anything. The backup did take a while though. I was a little worried at first that it was stuck.
zyrill, you need a donate button somewhere. I'm willing to donate to have cwm running on my tablet. CM 11 would be nice too but I'm just happy to be able to run Exposed and back everything up.
Mark
Oh Yeah
Oh yeah, I forgot to mention that I've got the WiFi only version. That's the 8080-f hardware version. The recovery block is the same.
B5Pilot said:
I installed this and it seems to be working. I backed up my current configuration but have not yet tried to restore anything. The backup did take a while though. I was a little worried at first that it was stuck.
zyrill, you need a donate button somewhere. I'm willing to donate to have cwm running on my tablet. CM 11 would be nice too but I'm just happy to be able to run Exposed and back everything up.
Mark
Click to expand...
Click to collapse
I tried the CWM recovery, and it didn't work for me. (Wifi-only HD+)
flashing worked fine, and I was able to boot into CWM
tried to run a backup, the display stopped changing at (quoting from memory here) "backing up sd-ext" - I have no ext-partition on my sdcard (64GB)...
1st try, switched off after ca. 2 hours: a folder clockworkmod\backup was created on the sdcard, but was empty
2nd try: let it run overnight until the battery ran out. Result: corrupted filesystem on the sdcard, had to re-install from scratch.
Does anybody have the original recovery.img for me to flash it back?
tdklaus said:
I tried the CWM recovery, and it didn't work for me. (Wifi-only HD+)
flashing worked fine, and I was able to boot into CWM
tried to run a backup, the display stopped changing at (quoting from memory here) "backing up sd-ext" - I have no ext-partition on my sdcard (64GB)...
1st try, switched off after ca. 2 hours: a folder clockworkmod\backup was created on the sdcard, but was empty
2nd try: let it run overnight until the battery ran out. Result: corrupted filesystem on the sdcard, had to re-install from scratch.
Does anybody have the original recovery.img for me to flash it back?
Click to expand...
Click to collapse
I may have a little premature in my enthusiasm. My backup included a full copy of my SD card which nearly filled the remaining internal memory. I never did try to restore the backup so I can't guarantee that it would work correctly.
I've started the process of compiling a version of CWM for the WiFi only version but I'm new to the whole process and it will take me a while to begin to figure it out.
Unfortunately I wasn't careful and never extracted the stock recovery before I flashed this version. I was double stupid and never tried to capture the ota to 4.4. I suppose you could do a factory reset and start over. Sucks I know.
Mark
B5Pilot said:
Unfortunately I wasn't careful and never extracted the stock recovery before I flashed this version. I was double stupid and never tried to capture the ota to 4.4. I suppose you could do a factory reset and start over. Sucks I know. Mark
Click to expand...
Click to collapse
I have captured the OTA to 4.4, so if you tell me how, I could try to extract the original recovery from it.
CM 11 would be great
Thanks for your attention to our HD+ tablets. I have B8080-F. Lenovo seems to be pretty slow in bringing new Android versions to this new tablet. It would be great to have CM 11 builds for this device. I have a Samsung Tab 2 7.0 that got new life after I installed CM 11 4.4.4..Just my encouragement to you folks who know how to build CM for the HD+.
Edit:
4.4.2 firmware have WiFi problems,problems with some apps like weather and so on. I went back to 4.3
Can anybody confirm the issues with the backup/restore process? It seemed to work fine for me. Maybe the exact steps to reproduce the mistaken behaviour will help us fix it. Also, I have the original recovery image, is it still needed?
Regarding CWM: I've just finished my PhD and am looking for a job. As soon as that's settled, I'll have time to work on other projects such as CM for our tablet. But in the meantime, if anybody makes any headway, simply issue a pull request and I'll include your work in our repository so everybody can benefit.
Cheers!
zyrill said:
Can anybody confirm the issues with the backup/restore process? It seemed to work fine for me. Maybe the exact steps to reproduce the mistaken behaviour will help us fix it. Also, I have the original recovery image, is it still needed?
Click to expand...
Click to collapse
thx, zyrill.
Well what cam I say, booted into recovery, chose backup/restore - backup and after a few messages the process seemingly stopped with "backing up /sd-ext" on the screen.
No ext-partition existed on the external sdcard, and there were about 10GB free on the internal and 27GB on the external, so wherever CMW tries to store it's files, I hope there was ample room.
I'd still very much appreciate the original recovery.img before I do any more experiments (it's the wife's tablet, after all
zyrill said:
Also, I have the original recovery image, is it still needed?
Click to expand...
Click to collapse
Hi zyrill, I appreciate that you don#t have much time now, but could you still please upload the original recovery?
I managed to get through a backup process in CWM without error messages. Let's trade hostages :laugh:
tdklaus said:
Hi zyrill, I appreciate that you don#t have much time now, but could you still please upload the original recovery?
I managed to get through a backup process in CWM without error messages. Let's trade hostages :laugh:
Click to expand...
Click to collapse
Sure, I'll upload the files once I get back to Germany next Tuesday. Am away and without access to something else than Android... I'll get right on it once I'm back.
Alright, excuse my belated reply. But here we go: I have uploaded the original recovery.img - see the attachment.
I have rooted through towelroot, haven't touched the recovery. I got the "b8080_s101103_140715_row_wifi" update but it failed to apply because of the LenovoSafeCenter.apk being altered.
Any way to update ?
Edit : I tried to restore the factory settings. The update still won't install.
DannyBiker said:
(...)because of the LenovoSafeCenter.apk being altered.
Click to expand...
Click to collapse
I don't think this has anything to do with towelroot as it doesn't alter any of your apk's. But anyway, for your convenience, here's an unaltered version of that file (see att.). Cheers!
Cool thanks ! I'll try that tonight...
Hello everyone I ma have problems on creating a nandroidbackup using TWRP 3.2.3.0
When I try to do a full backup, this error (createTarfork() process ended with error:255) pops up. Please help anyone
darko454 said:
Hello everyone I ma have problems on creating a nandroidbackup using TWRP 3.2.3.0
When I try to do a full backup, this error (createTarfork() process ended with error:255) pops up. Please help anyone
Click to expand...
Click to collapse
You need to look at /tmp/recovery.log while in recovery (adb pull it if you have to). Look in it for the last file that it tried to read before it gave the error. Your options are either delete that file or pull it then delete it. However, the file is corrupt in some way and the backup will never finish.
Sorry I a noob on this, I was able to get the recovery.log and Attached it but i dont have any idea where to find the error. Please help
thanks
darko454 said:
Sorry I a noob on this, I was able to get the recovery.log and Attached it but i dont have any idea where to find the error. Please help
thanks
Click to expand...
Click to collapse
I think It would be the " BASICDREAMS" but i cant seem how to delete it.. Would it be better to erase everything and start from the beginning? Im not sure what to do.
darko454 said:
I think It would be the " BASICDREAMS" but i cant seem how to delete it.. Would it be better to erase everything and start from the beginning? Im not sure what to do.
Click to expand...
Click to collapse
If you're fairly new to this then starting from a fresh install may be a better safeguard. However, you'll pick things up quicker if you determined enough. If you're simply wanting to remove the app BasicDreams, I went ahead and made modded a pre-existing flashable zip (all credit to Gizmo) just so you can remove that app. To use it, boot into recovery and flash it through there.
fuzzydorito said:
If you're fairly new to this then starting from a fresh install may be a better safeguard. However, you'll pick things up quicker if you determined enough. If you're simply wanting to remove the app BasicDreams, I went ahead and made modded a pre-existing flashable zip (all credit to Gizmo) just so you can remove that app. To use it, boot into recovery and flash it through there.
Click to expand...
Click to collapse
Thanks!!!
fuzzydorito said:
If you're fairly new to this then starting from a fresh install may be a better safeguard. However, you'll pick things up quicker if you determined enough. If you're simply wanting to remove the app BasicDreams, I went ahead and made modded a pre-existing flashable zip (all credit to Gizmo) just so you can remove that app. To use it, boot into recovery and flash it through there.
Click to expand...
Click to collapse
I just tried the "remove_basicdreams.zip "and says script succeeded but when i try to backup again it still has the same error.
what should i do next ?
thanks