Followed the great guide for my SGH-T859 for rooting and custom recovery. However I want more.. Don't we all.... This tablet is overall pretty nice and could really use it.
Problem is I am trying to install CM9 nightlies from 8-19-12 and for whatever reason I am having an issue.
Everytime I try and install it I get a message that states error and status 7. I attached a picture for reference.
Any help would be greatly appreciated.
https://picasaweb.google.com/106963773890259250828/Misc?authuser=0&authkey=Gv1sRgCJnK0OaNrIu7Fg&feat=directlink
Assert 7 errors come about because of recovery issues if I'm correct...never encountered that myself so you'll have to search around a bit more. Use "Assert 7" in your search string. Good luck!
Related
Hey guys,
Im not new to flashing roms etc,
but this is the first time i have so much trouble with it.
I read the streak how to PDF and followed the instructions on installing superboot.
when i installed superboot, the phone reset itself, and when it turns on, the dell logo shows up and the "home and menu" led starts flashing on and off and the restarts again.
I tried following the instuctions on how to restore the phone, but none of it worked. i specifically followed this guide: http://forum.xda-developers.com/showthread.php?t=805112
and when i try to flash the update.pkg, i get an error at the end about the boot bin or something like that.
anyone have any ideas?
Thanks!
I heard something about a QDL tool i could use...not sure what that is and i couldnt find an exact answer searching the forums.
any help would be greatly appreciated!
EDIT: found a guide on using the QDL tool, im going to try it now wish me luck lol
If u got yours from best buy u need to use QDL. Read carefully and just do as it says
thanks for the tip, it is indeed the best buy exclusive white one....running qdl as we speak
ok everything is good now!
i just need to figure out why when i try to install dj steves rom it gives me
"failed to verify signature"
ok so now i am having a hard time rooting the phone.
I am using the android 2.2 provided from QDL and am trying to root via universal androot which isnt working for me.
any other ways i can root?
note: im using a best buy dell streak
If you are updating to his 1.6 then you dont need to root it.
It it pre-rooted
thanks, I figured it out.
It turns out that the "how to pdf" (while an amazing guide) linked me to outdated versions of the the recovery which is why it would not work.
everything is working now,
running steves 1.6 and loving life. Thanks every one for your help!!!!!
MarcMaiden said:
Hey guys,
Im not new to flashing roms etc,
but this is the first time i have so much trouble with it.
I read the streak how to PDF and followed the instructions on installing superboot.
when i installed superboot, the phone reset itself, and when it turns on, the dell logo shows up and the "home and menu" led starts flashing on and off and the restarts again.
I tried following the instuctions on how to restore the phone, but none of it worked. i specifically followed this guide: http://forum.xda-developers.com/showthread.php?t=805112
and when i try to flash the update.pkg, i get an error at the end about the boot bin or something like that.
anyone have any ideas?
Thanks!
Click to expand...
Click to collapse
Not Android Development
Please Post in the Correct Forums
Moving to General
ok so I try to load a Update.pkg file and i get the following error message.
FOTA model name mismatched
what is the FOTA?
Hello everybody!
I'm kind of a newbie when it comes to SGS2 so I apologize in advanced if I come out a little stupid (this is my sister's device, I have a Nexus S, which I got exactly to avoid all the difficulties Samsung put in the way of devices like this)..
I've been trying to change my rom to CM7 latest nightly (#34), and in order to do that I must wipe all data andbackup my curret rom, when I try to install the rom and do all of those things with Rom Manager Premium, it keeps telling me something along the lines of "failed to verify whole-file signature"...
I've searched for a solution, and I understood it was something about the 3e upgrade system and that it has something to do with the kernel, but even changing the kernel, I had the same error, if anyone can please help me with this I'll be very grateful.
P.S. The device is rooted with CF-ROOT KG6
P.S.S. Please try to explain as simply as you can
Never mind, it worked out for me, you can delete this thread
SMan9090 said:
Hello everybody!
I'm kind of a newbie when it comes to SGS2 so I apologize in advanced if I come out a little stupid (this is my sister's device, I have a Nexus S, which I got exactly to avoid all the difficulties Samsung put in the way of devices like this)..
I've been trying to change my rom to CM7 latest nightly (#34), and in order to do that I must wipe all data andbackup my curret rom, when I try to install the rom and do all of those things with Rom Manager Premium, it keeps telling me something along the lines of "failed to verify whole-file signature"...
I've searched for a solution, and I understood it was something about the 3e upgrade system and that it has something to do with the kernel, but even changing the kernel, I had the same error, if anyone can please help me with this I'll be very grateful.
P.S. The device is rooted with CF-ROOT KG6
P.S.S. Please try to explain as simply as you can
Click to expand...
Click to collapse
1. Go to recovery mode manually once you downloaded the latest CM7.
2. Wipe full and cache too
3. Select install from zip. Find clockwork folder enter, enter download, enter get, you should see your CM7 zip file.
4. Select and install.
Normally happen first time going into CM7.
Send from my 'iPhone Killer' Samsung Galaxy S II using Tapatalk
Hi guys
My dad's tablet is messed up after an update from Lenovo. Tablet wasn't rooted nor anything. It is stuck on the "Lenovo" boot screen. I tried wiping the cash, factory reset, no luck.
Then I tried to download the OTA files from Lenovo site and update from the SD cards with no luck either.( downloaded all the files from A400 to A310_02_0024_0065. Each time I try to use an update, I get a message with the version of the previous update...
Each time I try to use an update (for example A310_02/0024_0065), I get the following message:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0060_US:user/release-keys" || "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0065_US:user/release-keys"
E:error in /tmp/sideload/package.zip
(status 7)
installation aborted
Click to expand...
Click to collapse
For example A310_02/0024_0075), I get the following message:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0066_US:user/release-keys" || "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0024_0075_US:user/release-keys"
E:error in /tmp/sideload/package.zip
(status 7)
installation aborted
Click to expand...
Click to collapse
And so on and so forth...
The lenovo site doesn't have any version earlier than the A310_02_024_065...
Anyone has an idea about what 's going on?
The tablet is 1838-CTO.
Anyone?
paricitoi said:
Anyone?
Click to expand...
Click to collapse
Hmm the only thing I can think of is are you using the correct versions of the updates? There are different ones for us, row, we, and so forth. Secondly do you recall what update were you on when you tried to update? Because these are incremental updates you can't revert back to previous updates or skip any if you were on 65 then you have to flash 75 if you were on 75 you have to flash 86 if on 86 you have to flash 89 and so forth. I had hard time updating because I was trying to skip straight to ICS from 75 which isn't possible. You said you never rooted so that means you don't have custom recovery which should make you good to go. Make sure you are flashing the updates in the right order should work then.
hatlesssandman said:
Hmm the only thing I can think of is are you using the correct versions of the updates? There are different ones for us, row, we, and so forth. Secondly do you recall what update were you on when you tried to update? Because these are incremental updates you can't revert back to previous updates or skip any if you were on 65 then you have to flash 75 if you were on 75 you have to flash 86 if on 86 you have to flash 89 and so forth. I had hard time updating because I was trying to skip straight to ICS from 75 which isn't possible. You said you never rooted so that means you don't have custom recovery which should make you good to go. Make sure you are flashing the updates in the right order should work then.
Click to expand...
Click to collapse
The Tablet is a US one. I also suspected the order of the updates but as I said, the oldest update available on Lenovo site is the A310_02_0024_0060_US yet when I try to use it, it complains about a previous version.
Do you know where I can get updates previous to A310_02_0024_0060_US?
Hello, I just fixed my tablet when having the same error as you.
Flash this format.zip:
http://ubuntuone.com/4zKT1jqeqhR8qdGh2y4TaM
What it does is self explanatory.
Reboot when done and then see if it works. If it does not. Flash one of these roms mad for the tablet found here (after using the format.zip):
http://forum.xda-developers.com/showthread.php?t=1846044
You kind of resurrected this thread lol. The issue they would have with that is they weren't rooted, so they wouldn't have CWM.
da_reeseboy said:
You kind of resurrected this thread lol. The issue they would have with that is they weren't rooted, so they wouldn't have CWM.
Click to expand...
Click to collapse
I just wanted to help :angel:
I see many many mega tones of threads online that have the same bricking problem and they all remain unsolved. most of them had rooted devices too.
Destreza said:
I just wanted to help :angel:
I see many many mega tones of threads online that have the same bricking problem and they all remain unsolved. most of them had rooted devices too.
Click to expand...
Click to collapse
All good
I'm one of the bunch of guy that have this tablet bricked, and with the bootloader locked by Lenovo.
The only thing we can do for the moment is:
Keep the pressure on the lenovo forum to unlock the bootloader.
Open formally support tickets about bricked Thinkpad Tablets to Lenovo
I'm also documenting all the stuff I'm finding on the XDA Wiki for this tablet.
http://forum.xda-developers.com/wiki/Lenovo_ThinkPad
Regards
Martin
Thank you soooooooooooooo much
Destreza said:
Hello, I just fixed my tablet when having the same error as you.
Flash this format.zip:
http://ubuntuone.com/4zKT1jqeqhR8qdGh2y4TaM
What it does is self explanatory.
Reboot when done and then see if it works. If it does not. Flash one of these roms mad for the tablet found here (after using the format.zip):
http://forum.xda-developers.com/showthread.php?t=1846044
Click to expand...
Click to collapse
my think pad tablet was rooted with clockwork and cygen ROM and was stuck at lenovo screen for 4 months. i only had to use the format file and it worked.:laugh::highfive: THANKS SO MUCH!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Hi.
It seems that I have a brick like this on the Thinkpad Tablet 1. It just show the Lenovo static logo.
The only good things is that I have CWM V6.0.1.2 installed and seems to works fine.
Any tip on which file can I flash to try to recover this tablet?
Regards
Hi
Can it be possible to repost the format file or include a working link.
Thanks !
Well I used TWRP to install a boot.img for my Nexus 7. Turns out I downloaded the wrong file, and now I can't get my device past the Google Screen after I rebooted it.
So far I've downloaded another boot.img and tried using that to solve my problem, that didn't work; it would end up stuck on bootloader screen frozen or saying "booting modified img"
I've used almost every recommended solution on Nexus Toolkit and all of them did nothing to help, Including downloading stock images, Restoring stock kernel, etc.
I don't know if perhaps I could have the build number wrong for the toolkit, but I'm not able to see what build it currently is since I can't get pass the google logo. I've done almost everything and now I am completely clueless as to what I can do to fix this. Any help would be deeply appreciated.
Had a similar prob the other days and i solve it fro here
http://forum.xda-developers.com/showthread.php?t=2206303
Post number 8 helped me because wugs toolkit has an option to return stock on a bricked device...
Stop relying on toolkits and learn to use fastboot and adb. It helps tremendously when you are having problems. It also prevents you from just getting clicky and selecting every option in hope that something fixes it. Follow the directions in the sticky on flashing a factory ROM/return to stock. It has all the information you need to fix your problem.
Sent from my Nexus 7(2012) that has zero issues.
So, I can't remember what I did to this device, exactly. I got it already in a bootloop. I had seemingly fixed it for a few weeks, but then it started rebooting randomly and then eventually got into another bootloop. I can't remember if that just happened one day or if I was trying to fix the random reboots.
I stopped working on it when a family member gave me their old Nexus 5X. But the other day my Nexus 5X entered into a bootloop because of its well known hardware problem (I think anyway, I wasn't doing anything that should have bricked it). So I decided to pull out the old Galaxy s5 and see if I can fix that instead.
Normally when I flash ROMs onto devices, I do it when the process for the device is pretty well established. As we all know, Samsung devices aren't the easiest to work with. So I remember having to do a bunch of extra ****, download Odin and so forth.
By the way, I have the AT&T G900A version. I boot into recovery and see that it boots into CWM, thats good news obviously. I pick "update through adb". I run ADB through command prompt (btw, someone should update the guides on this site to mention that Powershell doesn't play nice with ADB commands, that was like 20 minutes of hair pulling frustration) and it recognizes the device. I wipe all the user data and cache etc and attempt to flash a custom ROM I found on this site: APTOS found here.
I get an
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:footer is wrong
E:signature verification failed
So then I downloaded the stock firmware ROM titled "SM-G900A 4.4.2 G900AUCU1ANCE Firmware.rar" and get the same errors.
So, obviously I am forgetting something. I know there are a lot of guides on here and the answer is probably out there somewhere, the problem is that most of those guides are for people starting at square 1 without CWM or TWRP installed. Can anyone help me from where I am at? I uninstalled Odin a while ago but could definitely reinstall it. Was hoping to do this from where I am at, since CWM is already installed.
Anyone have any ideas on what step I'm forgetting? Do I need to flash other things before the ROM? Should I just start completely over with ODIN and the rest of it?
P.S. I have more experience with TWRP than CWM but I remember having trouble getting TWRP to work but did manage to get CWM to install as an alternative.
Thanks in advance!