Related
welcome
Today a customer brought me a tablet lenovo thinkpad type :1838-22g which then starts remain in logo.
I managed to start in CWM and I look like in the picture.
The client says he did all updates OTA settings and that he knew would ics that version and that gave him a soft reset and the tablet has not started.
Now from what I know the problem is more complicated (we have a similar problem on asus tf300-TWRP jb .. wipe - and same)
What would I do sit ok?
* to try to update the stock firmware?
* do update with cm 10 custom rom?
Tb to say that I could not communicate with the tablet fasboot or in another mode.
I do not know which would be the best decision so that she would not ruin it even more.
Waiting for some answers
All the best
mihnea
can't you adb sideload or use a toolkit to push files to the device?
Sent From My Paranoid Nexus⁴
The Thanks Button Is There
To Stop Thanks Posts Filling
The Thread.. Use It!?
N1XM1X said:
can't you adb sideload or use a toolkit to push files to the device?
Sent From My Paranoid Nexus⁴
The Thanks Button Is There
To Stop Thanks Posts Filling
The Thread.. Use It!?
Click to expand...
Click to collapse
I belive YES...
I see that I started the tablet and my pc recognized tha tabltet... driver is problem but I thing i solved
do you have any ideea ?
Looks like your partitiontable is corrupt.
I don't know anything about this device, but if something in /dev/block/ is missing, then I would assume that the partitiontable has been corrupted.
That would mean you have to completely recreate it, using nvflash.....if you can do this with this device.
Good luck
Micky
Ameisentaetowierer said:
Looks like your partitiontable is corrupt.
I don't know anything about this device, but if something in /dev/block/ is missing, then I would assume that the partitiontable has been corrupted.
That would mean you have to completely recreate it, using nvflash.....if you can do this with this device.
Good luck
Micky
Click to expand...
Click to collapse
Should work use an original ROM flash in nvflash to reset all partitions. Happened to me on another device, I just reflashed with an original ROM. And all was OK
Sent from my K1 using xda app-developers app
rpalmerin said:
Should work use an original ROM flash in nvflash to reset all partitions. Happened to me on another device, I just reflashed with an original ROM. And all was OK
Sent from my K1 using xda app-developers app
Click to expand...
Click to collapse
Sorry but I don't know procedure and comands...
mihnea
could you solve this problem? it seems i have exactly the same problem. please help.
mihnea_gsm said:
Sorry but I don't know procedure and comands...
mihnea
Click to expand...
Click to collapse
mnb123123 said:
could you solve this problem? it seems i have exactly the same problem. please help.
Click to expand...
Click to collapse
Not for the moment but still working...
mihnea_gsm said:
Not for the moment but still working...
Click to expand...
Click to collapse
hmm, sounds bad, your last post was since a while. in any case i keep trying too.
actually for using nvflash some code that is not released would be needed, isn't it?
on another thread i asked the same question and i have some partial progress, i flashed format_data.zip from cwm and then it seemed that i won't have at least during that session the "cannot mount" errors, thus i could flash another zip, with custom firmware or whatever, or do a nandroid restore. but sadly whatever i did so far it is still frozen on lenovo screen (or cyanogenmod screen).
see here for further reference:
http://forum.xda-developers.com/showthread.php?t=1846044&page=75
Some update on my similar problem, maybe somebody can help:
Now i managed sometimes (quite rarely) that ext sd is visible in cwm, then i can flash the format_data.zip, after which i can mount /data,/cache,/system in cwm (but not /sdcard). latest i tried to restore a 75us_nobloat_root nandroid backup i found on the forums, after which it is constantly rebooting from lenovo screen. now again i can't mount anything, so until i see again ext sd and apply format_data.zip, i'm again stucked.
the restoring of the backup seemingly went fine, except some .android_secure.img missing. could that be the problem (see log)? also i think whatever backup (ics, cm10) i restored, the log was the same, i.e. no .android_secure.img found, but the rest looked ok. but whatever i restored, it was always stuck on boot.
any ideas?
nandroid backup restore log:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
Restore complete!
the above last line may suggest to people not reading the whole comment that restore was successful. it was NOT, so i'm still looking for ideas what to do.
My 64GB Nexus is now saying it has 23gb of total storage and 21gb available. I had to reflash the stock ROM after a failed twrp flash. Is there anyway to fix this? I have already tried reflashing and wiping the phone 2 times but the storage decreases each time.
Use a factory image and start over.
ericsignals said:
Use a factory image and start over.
Click to expand...
Click to collapse
I've already done that twice
Pilz said:
I've already done that twice
Click to expand...
Click to collapse
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
jhax01 said:
Double check and make sure you have the latest SDK and/or just download the latest regardless. N5 folks have been having similar issues since the Lollipop release.
Click to expand...
Click to collapse
I can try to redownload the SDK, but my question is what does the SDK have to do with losing space on my phone?
I don't pretend to know what the cause is behind it but when the 5.0 factory images were released, people who flashed it with an older version of fastboot were losing storage on the Nexus 5.
Sent from my Nexus 5 using Tapatalk
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Pilz said:
I fixed it after doing a factory reset then flashing it again. I double checked and I already had the latest SDK. Its really weird how it took flashing 3 times to work.
Click to expand...
Click to collapse
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
the.emilio said:
I am in the same boat. Even did a factory reset and flashed the factory image but still stuck with 23GB on my 64GB. What exactly did you do to fix this?
Click to expand...
Click to collapse
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Pilz said:
I re-downloaded the latest SDK and then reflashed the images again. It took a few times before it reset. I also used fastboot erase system if I remember correctly.
Click to expand...
Click to collapse
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
the.emilio said:
Did you flash each image individually since the flash all gives that no system.img error? Just want to make sure I can duplicate what you did.
Click to expand...
Click to collapse
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Pilz said:
I flashed each one manually. The bat file doesn't work so that's the only way to do it. I don't remember the order I flashed everything in, but I remember that I used fastboot to wipe the phone before flashing. I kept trying different things until it showed the right storage then I decrypted it and flashed TWRP and used CF auto root. One of my mistakes was rooting before checking because it was a waste of time if I had to flash it again.
I may have done a factory reset st one point but I don't remember because it was late and I was watching TV with my wife whole doing this.
Click to expand...
Click to collapse
Figured. I will keep trying. Thanks!
---------- Post added at 11:56 PM ---------- Previous post was at 11:08 PM ----------
After about 10 attempts it turns out all i had to do was fastboot format cache then fastboot format userdata. Reboot and boom restored to normal. LMAO! Wasted 4 hours tonight just for that. Live and learn!
Just do a factory reset in recovery WITHOUT reflashing and the problem is taken care of.
Seems a like a bug in the factory images that can cause of wrong partition sizes.
Worked on my N9 (which I already sent back to Google due to excessive lightbleed lol)
I had the same issue after trying to root the phone showed 23 GB.
I was able to get back to 53 GB after wipine cache and formatting user data, but that still seems like I'm missing something . I did not check how much storage was available before I started.
Can any one tell me what the storage numbers should be on like on a stock device with nothing installed please?
I remember hearing about this same issue with the Nexus 5. Don't recall the cause though. Sorry folks I know this post is useless I'm just excited to be getting my Nexus 6 so I perusing the forums.
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
rev89 said:
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
Click to expand...
Click to collapse
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
simms22 said:
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
Click to expand...
Click to collapse
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
simms22 said:
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
Click to expand...
Click to collapse
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
rev89 said:
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
Click to expand...
Click to collapse
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
simms22 said:
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
Click to expand...
Click to collapse
Nope, would have made life a lot easier if I did. I was just kicking myself in the ass for that earlier.
Edit: nvm, forgot you don't have adb access
Sent from my Nexus 6 using XDA Free mobile app
Thanks for the help guys. I'm just gonna start from scratch when I get home... god I hate not having a phone.
Yah I realized fixing permissions messes it up. And also if u wipe internal storage the phone looses the system ui and the back home menu buttons as well
well thats good to know. Will it still do that if I'm not encrypted?
rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
I can personally confirm the permission fix in TWRP recovery breaks the stock L5.0.0 and 5.0.1 and I assume probably most ROMs? There seems to be several threads about this.
githyanki said:
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
Click to expand...
Click to collapse
you can flash from a jump drive? I didn't know that
Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
wizard5007 said:
Hoping I'm not totally screwed here, but here goes. I'm swapping from one Nexus 6 to another. On stock 5.0.1 (still), rooted, and unencrypted. I made my Titanium Backups (always as a precaution) then booted to TWRP and made a nandroid backup. I was too tired to command line myself so I decided to use the Skipsoft Toolkit to pull my data. I got curious about a full backup option on there so I tried it out. First thing it did was boot an unsecured boot.img. Phone then boots back up and begins the encryption process. I knew I didn't want encryption, so I powered off mid-process. (Kicking myself for that now...) Now when I boot back up, I get the "Encryption Unsuccessful" message telling me that my data is unusable and that I must do a phone reset.
I can still get to the bootloader and boot into TWRP, but it can't see any of the data on the device--including the TWRP backup I made earlier today. Seeing as I didn't get any of my backups off before this happened, I need that TWRP or I will lose everything since my last backup on 11/6. Is there ANY way to still pull data from a partial but failed encryption? Please help!
Click to expand...
Click to collapse
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
zelendel said:
You most likely corrupted all the data on the device.
Not sure why you thought powering off during encryption would stop it and not cause corruption.
Also dont even think about restoring a nandroid on a new device.
Click to expand...
Click to collapse
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
wizard5007 said:
Because I wasn't thinking... I know--stupid. Is there no shot at recovering anything?
I'm switching from one Nexus 6 to another. Can I not restore a nandroid to an identical device?
Click to expand...
Click to collapse
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
How did you fix the issue?
zelendel said:
No, no you can not. A nandroid has device spicific files in it like GPS and IMEI info. Restoring it is just asking for trouble. Only restore USER apps and data everything else is off limits.
Click to expand...
Click to collapse
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
scryan said:
So what specifically is in /system or /data that would be so dangerous?
Have you ever actually done this, or are you just saying stuff you have read but don't fully understand?
If you backed up every single partition its a bad idea to restore to another phone... But simple backups are fine to restore cross device if you aren't including efs
Click to expand...
Click to collapse
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
zelendel said:
You do know who your talking to right? I don't read things. I do them. Been doing this for over 10 years now. So just maybe you might want to know who you are talking to first.
Click to expand...
Click to collapse
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
lol!
ok, both @zelendel and @scryan are right..
its highly not recommended to restore a nandroid onto a different phone if it contains system apps. that said, theres also a chance that it would be fine as well. its just that the system apps could not be supported(or could be) by the 2nd device. but even if they arent supported, it wont really harm your device, as you can fix whatever issues by just switching out the apps that are causing issues(then reboot).
scryan said:
Nope, no idea who you are.
All I know is how many times I have seen twrp backups restored on a phone it wasn't taken on with out issue?
Maybe you should actual read things and you wouldn't have an issue with it either?
Or... Care to actually explain the danger rather then just puffing your chest out because you have played with android smart phones for ten years (apparently since before it was released?)
Click to expand...
Click to collapse
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
zelendel said:
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
Click to expand...
Click to collapse
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
simms22 said:
the Dream(G1) was Googles android developer phone before the Nexus. while a lot of people did use and mod the HD2, the G1/Dream was getting most of the developer support.
Click to expand...
Click to collapse
I wouldn't say most. But it was close indeed. I had them both but focused on the hd2 mostly. God I miss truly open bootloader lol.
zelendel said:
....focused on the hd2 mostly.
Click to expand...
Click to collapse
I remember the HD2 as one of the best phone ever made.
zelendel said:
Well let's start out with the fact that when system apps are loaded the data loaded to is set to one device. By restoring that to another device messes it up and causes all types of issues with the app and system.
Also as stated above not all apps are compatible across devices. Could lead you to an endless bootloop.
See you have me twisted. I don't have to read about it as I do it everyday. As each device is different there is no telling that one thing will work for one but not the other.
As for doing this before android was released? Yes. Who do you think got leaks to run on wm devices before the first nexus was released? Xda and the legendary HD2.
I was modding devices before the first smartphone was even released. Then I became a moderator here. Which is requires a whole lot of learning. Like reading the source and knowing what does what.
Now you are more then welcome to flash someone else's backup, that is up to you but I will tell you that no one that knows what they are doing will do that.
Click to expand...
Click to collapse
Just wanted to chime in here and say, I agree 1000% that I would never restore a backup from one phone to another, unless I knew for a fact I could "rescue" the phone if it locked up/got fried/ruined from the restore..
And, I have been playing with cell phones since November 1983, the first day cell service became widely available in Chicagoland, and I have been modding/tweaking/hacking them pretty much since then, so I too have "extensive" experience about what may or may not work when doing something like this..
To each his own, but I would never do this..
need mmcblk0 for XT1925-3
or blank flash working
mmcblk0.img
Ambrosio71 said:
need mmcblk0 for XT1925-3
or blank flash working
Click to expand...
Click to collapse
Nobody?
Ambrosio71 said:
Nobody?
Click to expand...
Click to collapse
Well, to be honest you're kind of asking for a lot. An entire copy of someone's phone, every partition and all data.
I've seen it posted for a few devices in these threads before somewhere, but I've never understood why someone would need such a thing, so I didn't really pay too much attention.
nate1975 said:
Well, to be honest you're kind of asking for a lot. An entire copy of someone's phone, every partition and all data.
I've seen it posted for a few devices in these threads before somewhere, but I've never understood why someone would need such a thing, so I didn't really pay too much attention.
Click to expand...
Click to collapse
recover from a hard brick
Ambrosio71 said:
recover from a hard brick
Click to expand...
Click to collapse
Well, I don't have that particular variant, but if someone does want to create such a backup, they should be able to do the following:
1) Boot into twrp, plug into a computer.
2) adb pull /dev/block/mmcblk0 mmcblk0.img
Compressing that giant image should shrink it down considerably, so you won't have to actually post a 32G file or whatever.
And also just a note here, if you can boot into the bootloader and run fastboot commands, then you shouldn't need this anyway.
nate1975 said:
Well, I don't have that particular variant, but if someone does want to create such a backup, they should be able to do the following:
1) Boot into twrp, plug into a computer.
2) adb pull /dev/block/mmcblk0 mmcblk0.img
Compressing that giant image should shrink it down considerably, so you won't have to actually post a 32G file or whatever.
And also just a note here, if you can boot into the bootloader and run fastboot commands, then you shouldn't need this anyway.
Click to expand...
Click to collapse
in my case only the led flashes
there is still no blank flash file for XT1925-3
Ambrosio71 said:
in my case only the led flashes
there is still no blank flash file for XT1925-3
Click to expand...
Click to collapse
I'm curious how you ended up in this situation? How do you know that the OS is even the problem and it isn't a bad battery or something?
nate1975 said:
I'm curious how you ended up in this situation? How do you know that the OS is even the problem and it isn't a bad battery or something?
Click to expand...
Click to collapse
my version of Android was 8.0
I downloaded version 9.0 in .zip and put it in the internal memory, the system identifies the package and installs it normally as if it were an available update.
I had done this type of update before and never thought it would cause this type of problem.
This time, everything happened normally, but at the end of the update, the device needs to restart, but mine turned off and did not start, I put it on the charger and it was in the state it is in, with a flashing LED.
NOTE: this version of Android 9.0 for this device is official, however, it is a beta version, so it is only installed via .zip in the internal memory.
Ambrosio71 said:
my version of Android was 8.0
I downloaded version 9.0 in .zip and put it in the internal memory, the system identifies the package and installs it normally as if it were an available update.
I had done this type of update before and never thought it would cause this type of problem.
This time, everything happened normally, but at the end of the update, the device needs to restart, but mine turned off and did not start, I put it on the charger and it was in the state it is in, with a flashing LED.
NOTE: this version of Android 9.0 for this device is official, however, it is a beta version, so it is only installed via .zip in the internal memory.
Click to expand...
Click to collapse
Huh. Ok, so someone gave you an official beta, but won't supply you with the file you need to recover? Very strange. Hopefully someone else has that same device and can create a backup that you can use.