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.
Related
Im getting this error and force close on one of my Heros when I try installing any of my apps on any of the 2.1 roms. Im coming from Fresh 1.1 and following the same procedure I used on my other Hero on which the market is fully functional. Ive wiped everything over and over and cleared data on anything that looked like it at to do with the market. I also tried fix apk mismatches from recovery. Short of RUU which Id like to avoid if at all possible Ive tried everything else I can think of. In searching I have come across this error code on other android phones, but nothing on the hero and nothing specific to trying to install apps. So has anyone else seen this? And would RUU do anything a full data wipe didnt already?
Reading instructions has its benefits grasshopper...
Download the latest recovery and throw it onto your SD Card, boot into the old version of recovery and flash the new recovery as a .zip update, reboot into recovery again and then wipe your phone again, then install android 2.1, don't reboot yet, make sure your rom either has it's own custom kernal or download one for 2.1 and flash it, open up adb and clear dalvik cache and boot cache, then reboot your phone and you should load without any problems.
Thanks. But I did that from the get go. Aside from flashing a kernal, but Im running Darchtrev2 on the fully functional Hero that I mentioned and thats got a custum kernal built into the rom. So thats what I started with on the second one using the exact same process without success. Does wiping from adb do more than wiping from recovery? Thats one other thing I didnt do after the initial install.... But do understand you correctly that you have seen this specific error before?
Just bumpin the tread in hopes of finding a solution. I dont even mind gettin flamed for asking a stupid question if I could get linked up with a fix! lol I see its getting views, just no ideas I guess... It sucks cuz everything else works fine except the market. I get the list of my downloads, when I tap on one to install I the download button instead of the install button, so Ill tap on it and I get get the progress bar saying its downloading. When it gets to 100% I get the error and force close... Anyone?
I would try wiping again then flashing fresh 1.1 see if that boots and everything works ok then I would redownload the recovery and flash that still running fresh then reboot make sure everyhting is cool, then redownload whatever 2.1 rom you want and wipe and flash.
doing this serves 2 purposes
1. make sure that somewhere along the line none of the files corupted
2. if you still have the same problem then it will let you know where the problem is coming from.
just process of elimination
if you still have problems after that then I would say RUU, yes it is different than just wiping from recovery as it restores a completely stock image and gets rid of everything else. all a data wipe really does is get rid of user data.
just my opinion.
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Thanks for the reply and for giving me something different to try. I hadnt thought about trying that. Frustration I guess! It makes sense though. Ill give it shot. Thanks!
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Yeah, Ive been thinking about RUU'n too just to see if making a fresh start would make any difference, but after all the time I spent getting the one Hero working like I want on 2.1 and the troubles Ive had with the second and what Ive read about people bricking trying to RUU or flash recovery Ive been kinda hesitant....
willy900wonka said:
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Click to expand...
Click to collapse
Thanks. I dont know that Im quite that knowledgable though. Im sure I could read a logcat... understanding what the hell I would be reading is something else again. Saving the url though in case I need to dig deeper. Thanks for the reply.
wtphoto said:
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Click to expand...
Click to collapse
Sometimes it's just fun to RUU and do everything again
Alright if you're still having problems then just follow these steps:
Boot into recovery and make a nandroid back up just in case something goes wrong.
Download the latest version of your current 2.1 rom and reflash it from Recovery.
Open up adb and mount the /data directory (adb shell, mount /data)
Enter the following two commands in adb: rm -r /data/boot-cache , rm -r /data/dalvik-cache
Go Back to ADB and type the following commands: cd /data/data/com.android.vending , rm -R cache
Fix UID Mismatches using the tool in Recovery and then reboot your phone
regaw_leinad said:
Sometimes it's just fun to RUU and do everything again
Click to expand...
Click to collapse
or NOT!
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
You should have updated to the latest ruu...
wcgbmd said:
You should have updated to the latest ruu...
Click to expand...
Click to collapse
The latest RUU? I used the 1.56..... I did get it working tho. Flashed the mms. fix zip. Just wasn't expecting to have to as I didn't with my other hero. Don't know what the difference is between the two devices. Both are google branded, but the second one fought me every step of the way.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
First, sorry for the bump.
I just started getting this error and wanted to know if you figured out exactly what it was so I didn't have to go through that whole RUUing process. Thanks.
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
You're the bomb. That worked like a charm.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
Cant believe nobody wrote this first
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
I was having the same problem on DC a couple days ago and that fixed it for me. I was reading this thread wondering why no one had mentioned it yet.
I keep getting the constant nexus loop I am trying to root and I cannt get past that any advise?
Please and thanks
schartzr said:
i keep getting the constant nexus loop i am trying to root and i cannt get past that any advise?
Please and thanks
Click to expand...
Click to collapse
briiiiiick
check out the search feat too
I need a System image I believe do you know where i can get that at? And the search feature is not working right now, and I need to get my phone back up and working ASAP.
Thanks
schartzr said:
I need a System image I believe do you know where i can get that at? And the search feature is not working right now, and I need to get my phone back up and working ASAP.
Thanks
Click to expand...
Click to collapse
Not sure where the .zip is to flash the entire system..in fact, I don't think that was officially released yet. If you managed to get Clockworkdmod installed, I know there is a system image you can flash in the Dev section here.
Or If I have a nandroid back up how can I get that on m y phone to run that? I have it on the SD part of my card but doest show in the back up and restore file
schartzr said:
Or If I have a nandroid back up how can I get that on m y phone to run that? I have it on the SD part of my card but doest show in the back up and restore file
Click to expand...
Click to collapse
Go into recovery and re-flash your nand back up... have your tried that?
edit: damn. didnt realize. see? wtf sammy/goog. WHY WOULDNT YOU HAVE A MSD SLOT??!
allen099 said:
Not sure where the .zip is to flash the entire system..in fact, I don't think that was officially released yet. If you managed to get Clockworkdmod installed, I know there is a system image you can flash in the Dev section here.
Click to expand...
Click to collapse
I do have clockwordmod I am guess you mean when I can get to the clockworkmod recovery screen I can get there
schartzr said:
I do have clockwordmod I am guess you mean when I can get to the clockworkmod recovery screen I can get there
Click to expand...
Click to collapse
You can try flashing these:
1- http://forum.xda-developers.com/showthread.php?t=877601
2- http://forum.xda-developers.com/showthread.php?t=875875
3- http://forum.xda-developers.com/showthread.php?t=875184 (if you really know what you're doing)
I assume you understand how adb shell works and all that, since you're dabbling in all this goodness .
Good luck, young samurai!
How would I write a system image would it be fastboot flash system system.img?
guys thanks I got my phone fixed Thanks for all your help
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
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...
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
Have you tried flashing a factory IMG?
Sent from my Nexus 6P using XDA-Developers mobile app
XAL2 said:
Hey there. I was wondering if anyone could help me out. I was running CM 13 on my Nexus 6P for a while but then I kept getting this message that said that there was something wrong internally and that I should contact the manufacturer. I just ignored it. I decided to download the latest nightly and try to freshly install it. I did a full wipe and installed the new CM13 nightly (7-1) and then gapps. When I tried booting the phone up it wouldnt go into the system. I went back into the recovery and tried installing a back up. I did that and tried booting up again into that restored backup and stilled didnt work. So I'm stuck right now with a non working phone. My bootloader is unlocked if that helps any.
Click to expand...
Click to collapse
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Heisenberg said:
What options did you select when creating and restoring your backup? And, as above, have you tried flashing the factory images?
Click to expand...
Click to collapse
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
XAL2 said:
I actually just did that. All is well. I was having trouble with fastboot commands because my phone wasnt being recognized but i just googled nexus 6p drivers installed them again and ran through the fastboot commands to get my phone back to stock.
Click to expand...
Click to collapse
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
XAL2 said:
I actually have a question about that. When you say check vendor boxes are we supposed to check them both or just the vendor box and not the vendor image box to backup?
Click to expand...
Click to collapse
Only the ones that I mention, leave the system image and vendor image boxes alone.
Heisenberg said:
Cool, glad you got it worked out. With your backup you may have selected the wrong options, have a look in my guide, there's a section dedicated to backups.
Click to expand...
Click to collapse
Heisenberg said:
Only the ones that I mention, leave the system image and vendor image boxes alone.
Click to expand...
Click to collapse
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
XAL2 said:
Noted for sure. Thank you for your help. Oh hey can you answer one question for me though? When I was running CM13 how come I always got that alert that something internal was messed up and that I should contact my manufacturer? Also how come when I tried to do a clean install it wouldn't boot? Like that confuses me a lot because it was a clean install but I ran into problems.
Click to expand...
Click to collapse
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Heisenberg said:
Perhaps you had the wrong vendor image installed? Other than that I'm not sure. As for why the clean flash didn't boot I'm not sure either, there could be multiple causes for that so it's a bit hard to narrow down.
Click to expand...
Click to collapse
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
XAL2 said:
Oh man who knows. Thank you again though for the help and answering to quickly! Also thank you for that guide! Saved my phone's life. Lol
Click to expand...
Click to collapse
No probs, happy to help.