Database Info

[Q] I think I killed my Nexus S! Please help! (unlocking process/rooting stuff)

So, this is what has happened so far:
I googled for a small and easy to follow guide to unlock my phone so that I can later on install a custom rom. I followed the steps provided here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
What I didn't notice on the first place was the "UPDATE: DO NOT FOLLOW THIS GUIDE INSTEAD Please see new root method which works on all Nexus S and Nexus S 4G!" link. Don't ask why - really don't know.
The result was having my Nexus S stuck on a screen that shows Google logo on the middle and an unlocked padlock on the bottom.
It seemed, or to be exact, I figured out that, the problem was the .img file mentioned on some point in the middle of this.. tutorial.
So, I decided to follow the newer guide that can be found here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Although all went well (didn't have to go all over the same processes up to the .img installatin point), I ended up with the same screen that shows Google logo on the middle and an unlocked padlock on the bottom.
I figured out that I could just install a rom at this point, and decided that I should go back to stock. So, I followed this guide here:
http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
But, when I choose to install the .zip file, I get this error:
assert failed: "getprop ("ro.product.device") == "crespo" || "getprop ("ro.product.device") == "crespo"
E: Error in /sdcard/i9020t_i9023.zip
(status 7)
Installation aborded
..let me add to this point that I have bought my Nexus S from EU, it is an i9023. Let me also add that all I wanted is to flash an ICS rom and I think I have ended with a f****d device I don't know what to do with!
Any help, really, would be so much appreciated since I need to use this phone. I have a backup for calls etc but I need some smartphone features!

I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.

nickmv said:
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
Click to expand...
Click to collapse
Yes, I can enter this menu - there already. My model is an i9023GSM.

OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?

nickmv said:
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
Click to expand...
Click to collapse
You gave me the good news so, thank you for that. Now, I should follow this guide and come back in case I have a problem.
As far as the rom, I wanted to flash an ICS since I cannot wait any longer for Google to release the official update. But right now, anything that can get my device up and running would be really good!

Edit: nvm. >_<

kijp15 said:
Why don't you just use shabby's one click root. Simple & much easier. Saves all sorts of troubles.
Click to expand...
Click to collapse
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!

nickmv said:
but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
Click to expand...
Click to collapse
OK, stuck already. On Part 2 what I understand is that I have to open the CMD and copy-paste the path to the "tools" folder? Because this is what I do, and after - since this is what I have understand - I type "fastboot oem unlock" and I get "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
What do I do wrong?
EDIT:
Tottaly stuck on Part 2. It seems that there is no fastboot.exe file inside "tools" folder. I don't think the problem is something else - I'm sure I give the right commands since I tryied for fun another folder I have with fastboot.exe inside and it worked - to be exact it just gave me a FAILED messsage since device is already unlocked. Plus, regarding Part 3, Step 1, the first file for download is missing so I used the second link and downloaded 5023-cyan file. Hope this was a right move to do.
EDIT 2:
Ok, here is the story so far: I followed the guide given step by step. The USB drivers has been installed correctly so the device can be connected to the PC.
In the "tools" folder there was no such fastboot.exe file so I manually added one that I've found on the newer guide given on the 1st post. The unlocking process is failing because the device is already unlocked.
I did manage to install after this, the 5023-cyan.img file since this is the only link working from Part 3, Step 1. This gone well too!
Now, I couldn't go on with Part 4, I mean, I could not install the .zip file as it describes so through recovery mode I installed the .zip file succesfully (confirmation message to Nexus S screen).
I reboot and still get the same Google logo on the middle and an unlocked padlock on the bottom.
I cannot understand what I do so wrong? Oh, I'm so disappointed..

OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?

http://forum.xda-developers.com/showthread.php?t=1063664 or use ROM manager and select Stock ROM (you should then receive OTA upgrades to 2.3.6).
On the latter: You colud just back up different ROMs and switch between them using CW.

skatastamoutrasas said:
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
Click to expand...
Click to collapse
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness

mixtapes08 said:
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
Click to expand...
Click to collapse
Can you give me a CM9 kangs link since as new here, I'm kinda lost?

Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?

skatastamoutrasas said:
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
Click to expand...
Click to collapse
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img

kijp15 said:
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
Click to expand...
Click to collapse
Worked just fine! Thank you!

skatastamoutrasas said:
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
Click to expand...
Click to collapse
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.

nickmv said:
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
Click to expand...
Click to collapse
It did worth the hassle, that's for sure. Now I think it's so easy to unlock a Nexus plus I now have a little more knowledge regarding Android .
I will stick with CM 2.3.7 as it looks just fine. I don't care about warranty, I don't think I will ever need the official service for a software issue. Now I have to re-install my apps, re-sync my accounts and setup the phone the way I want it. It will take a little more time.
But I'm glad that I pulled this through - with your help of course! Guys, you rock!
I wish that I'll be as helpful as you at the near future.

Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
MAKE SURE THAT YOU HAVE CLOCKWORKMOD PERMANENTLY INSTALLED BEFORE DOING THIS. It saves time if you mess up. Also, make sure you get the latest gapps HERE
Instructions:
1. Go to clockwork recovery
2. Select data/factory reset/wipe
3. Select clear cache as well
4. Adv Mounts and Storage > wipe /system (note, this wipes android off the phone. It's a good idea since youre going from ver 2.x to 4.x)
5. Choose "flash from zip" (or whatever it's called.....NOT flash from update.zip)
6. Flash the cm9 update file first, then flash the kernel of your choice, then flash the gapps file.
7. Back out of the menu and select reboot.
Take note though, that the new ICS OS has incompatibilities with certain apps while GPU rendering is turned on, etc. It'll prob reboot on you sometimes, etc. For the most part it's stable, but that's completely subjective.
If you do run ICS, make sure you turn on GPU rendering in Dev Options. It takes full advantage of the GPU for UI animations, etc. Sometimes there's a stray app here and there that doesnt play nice, and you'll notice if the window looks really tiny or funny. Turning it off will fix the problem.

nickmv said:
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
Click to expand...
Click to collapse
Two questions:
The link you give me to download the ICS rom keeps loading for ever. So, I choosed this one instead:
http://forum.xda-developers.com/showthread.php?t=1356228
Right or wrong thing to do?
It it essential to install a custom kernel? I ask because I forgot to copy/paste the .zip file and due to lack of time, I procceded without it, installing the ROM and G-APPS.

[Q] Stuck booting

Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag

You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!

Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)

shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.

berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington

When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.

shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.

Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag

Won't upgrade Factory Software, Wont enter recovery. Hangs on boot

First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated

A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.

The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.

berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.

RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!

@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.

RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.

berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts

Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html

berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.

What did the trick to get fastboot working?

berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.

berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.

[ROM[6.0.1][VFD-1400][OFFICIAL] Vodafone Prime Tab 7

Pretty tricky to find anything for this tablet, but I managed to find a way to get an official image.
What you need:
Alcatel Mobile Upgrade Q 5.1.7 (or newer), get it here.
This will overwrite all your data on the device.
1. Install Mobile Upgrade Q
2. Run "C:\Program Files (x86)\Mobile Upgrade Q\tool\usb_driver\installdriver\DriverInstaller.exe" to install the USB Drivers.
3. Enable USB Debugging
4. adb reboot edl
5. Mobile Upgrade Q and select "VF1400" (note it also lists 9030G and 9030Q, the unbranded variants of this tablet (yet unreleased?), but unfortunately you can't flash these, it will just download the Vodafone branded image)
6. It will download the image files into "C:\Program Files (x86)\Mobile Upgrade Q\bin\download" (note while it's downloading the image files, these are just filled with 0s)
7. After it downloaded the image it starts flashing ("initialisation") and you can copy the files to some place safe (from bin\VF1400-2AVDXXX), it deletes some after it's done
B1BEB0B0CD00.mbn is the boot image, R1BEB0B0CD00.mbn the recovery. Some of the files have partition information, probably can use these to flash with QPST.
Going to have a look into compiling a TWRP, now that I have the kernel

Also, Alcatel seems to have released a *very incomplete* kernel source (build scripts and other things missing) over at https://sourceforge.net/projects/alcatel/files/, see OT_VDF_1400_20160520.tar.xz.
A bummer since the kernel in the official image seems to have all kinds of debugging stuff enabled.

Some more findings. You can coax SUGAR QCT_SP (and maybe Alcatel Mobile Upgrade Q 5.1.7?) into flashing any images.
Before starting SUGAR QCT_SP, copy your backup of the VF1400-2AVDDE1 folder into bin/. It should flash these files.
I flashed a ported recovery, but I couldn't boot it (always boots stock recovery). I guess because of secure boot? Read something about the recovery-from-boot.p file...
Don't worry about bricking, you can get the tab into edl mode with an edl cable. http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/

Some progress, if anyone cares :laugh: (doubt it).
Flashed boot with altered build.pros, selinux is off, but adb root kills the adbd.
Same on recovery, but kind of pointless with zip verification. Now it's either compile a recovery or add a custom key too boot and sign the supersu zip myself.
Also flashed a slimmer system, minus all the google apps I don't use anyway. Stock image carries 1GB of empty space that is being flashed every time

One more interesting thing: You can get into fastboot by flashing a recovery with the wrong kernel and then booting to recovery. Fastboot is crippled though and does nothing useful, can't even flash with it.
Btw to turn off the device if you are stuck in a bootloop to recovery: With usb cable unconnected, hold Power and Volume down. It screen goes black after 5 sec, keep holding the buttons. It should come up again and very shortly after, let go of the buttons screen when the screen goes black a second time.

So, at the moment there is no way to root?
Geeting the device tomrrow

Yes there is. After getting rid of selinux, you can get temporary root using dirty cow, or bake supersu into the boot or system image.
Also I'm working on porting a recovery. It works, more or less already.

I just flashed SuperSU via the recovery I ported. Seems to work

Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?

gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
I can upload it later.
Fastboot is crippled and you can't boot into it directly, at least on mine. Try booting into it (hold power + vol down). Otherwise see my earlier posts on how to do the initial flash. A little inconvenient, but it's only once
Will post detailed instructions with the recovery.

gella1992 said:
Nice! Is it possible to Upload your Recovery? Simply flash via Fastboot?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560

Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel: https://github.com/852Kerfunkle/android_kernel_vodafone_vfd1400
Works for booting into recovery.

While trying some things with caf android builds, I flashed aboot, thinking I could always get back into download mode with the makeshift EDL cable. Turns out you can't.
Do not mess with aboot unless you are 100% sure (unlike me). The device will only register as HS-USB Diagnostic 900E. Even with an EDL cable.
For anyone who did: your device is not dead, but it's a bit of a mission.
1. Take of the back cover: Remove the screw behind the sim/sd latch and open the device with one of these plastic opener thingies, start at the latch.
2. Bridge the pin marked on the image (take a cable and connect the pin to the ground of the usb connector, i.e. the metal bit).
3. Plug in the usb cable.
4. It should register as HS-USB QDloader 9008 (assuming you have the right drivers).
5. Flash with Sugar.

Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom

gella1992 said:
Hopefully everything is working great again!
Do you think it would be possible to port a Lineage OS to this Tab?
I know how to compile from source, but actually not developing a Rom
Click to expand...
Click to collapse
Yeah it's working alright again, thanks
I tried, no luck yet. Am stuck on a crash in libsdm. Once I had it boot to the point where it was initialising the apps (dexopt or whatever?), but it crashed right after.
For now I am focusing on codeaurora android. If I get that working, maybe the caf parts can be used to make a working LineageOS build.
I also have little to no idea how to do anything android related, so most of the time is spent reading and googling silly errors. Just give it a go, if you get stuck I can help out with what I found so far.

At the moment I am busy. Will give it a try when I have more time :fingers-crossed:

fused#1 said:
Working on a frankenkernel with some salvaged parts from the incomplete kernel source from alcatel:
Works for booting into recovery.
Click to expand...
Click to collapse
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:

nevexc said:
Are you still working on this ?
I'm currently considering the option of running a git diff against the CAF msm-3.18 "LA.UM.5.1-03210-8x37.0" TAG/branch, which the released incomplete kernel source appears to be based on.
Then going through the patches and applying them one by one on the newest CAF 8937 TAG/branch.
Although getting LA.UM.5.1-03210-8x37.0 to work with the patches applied would be nice already.
My ultimate goal is OMNI, im not interested in CM/Lineage.
Problem is at the moment i don't have much time for this.
But we'll see :good:
Click to expand...
Click to collapse
Hey,
That's pretty much what I was doing before I got caught up in other stuff
Was stuck at trying to figure out how to actually build caf android. Which of the files on the rom belong the the proprietary blobs and how to properly include them in the makefiles so it actually builds...
Hit me up with a PM, maybe we can coordinate our efforts :fingers-crossed:

Thanks for this Guide, but I have a quick question:
I am currently trying to restore my VF-1497 to a stock rom with Mobile Upgrade Q 5.1.7, but the Upgrader always kicks my Tablet out of edl, and throws the error:
'There is no greater version available to upgrade your phone, actual version of your phone is the latest'
Is there any way to restore this device back to stock?
Thank you in advance

ASP
Hi is there a custom "clean" firmware for vdf1400 that can go instead of the latest 6.0.1 150fkg1

bootloop - question on how to proceed

I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:

monogwai said:
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
Click to expand...
Click to collapse
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....

berndblb said:
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
Click to expand...
Click to collapse
I figured that would probably be the case. Now, it's been several years since I've used Linux (Ubuntu Feisty Fawn was the last time I used Linux, and that was just to hack a first gen Xbox), but i'm a command-line based OS guy from the days of old, so I oughta be okay. I'm sure one of the various and sundry tutorials here on xda will help should I get stuck.
So, that being said, I guess I just need to install a distro and grab some adb/fastboot drivers for Linux? Or is that all built in? Is the command line interface sufficient, or will I need some GUI like xwindows (sorry if my info is horribly dated, lol.)
I'd probably better do some reading.

Nobody has any more expertise to proffer?

monogwai said:
Nobody has any more expertise to proffer?
Click to expand...
Click to collapse
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary

berndblb said:
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
Click to expand...
Click to collapse
This is just the tip I needed. Big thanks!

Well, i assembled the troops- universal naked driver and minimal adb/fastboot on a fresh win 8.1 install. Bootit.ko file in my adb folder. Opened adb, plugged in tablet. Twrp starts. Hear the USB plug in noise, so adb is ready. Adb devices command, shows up recovery like it should. I then run a batch command to automate:
adb push bootit.ko /sdcard/
adb shell insmod /sdcard/bootit.ko
... as per the directions. I get this in response:
adb: error: connect failed: protocol fault <couldn't read status>: no error
on the first command, and 'no device found' on the second.
Now what?
Edit: nevermind. Added 'adb devices' to the batch file and it did it fast as anything. Lol.

New kink: adb command succeeded and i got fastboot access. Formatted 'misc' partition and rebooted-- still with the bootloop. I can still access fastboot, but that's it. Twrp always restarts. So, did SWIM bork the recovery partition too? Wondering if I should try re-flashing twrp, or downloading the original ASUS blob file and restarting from square one?
Edit:
Got impatient, started trying things. Links found thru the forums pointing to original ASUS rom blob are all broken, so i settled for starting with twrp. Downloaded freshest version from twrp.me compatible with the device and flashed it-- same result upon attempting to open twrp.
Took a break. Thought about it, and decided to fastboot erase recovery, and try flashing twrp again. Probably not a great idea... Now I get
Sending 'staging' <7210 kb>...
FAILED <data transfer failure (unknown error)>
So I guess there's a step after erasing to re-init the partition or something?
Just a note to anyone lurking - don't do stuff if you're only half-informed. You can be stupid and impatient like me and have broken stuff.

Impatience is a very bad advisor...
As long as you have fastboot you should be ok. Asus seems to have messed with their website again or they finally took the support pages down permanently.
I have a copy on my server and can upload it tonight.
Patience my friend, patience

berndblb said:
Impatience is a very bad advisor...
I have a copy on my server and can upload it tonight.
Patience my friend, patience
Click to expand...
Click to collapse
This is too true. That's why I threw in that little blurb. :good:
I'll await your link with bated breath.

Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again

berndblb said:
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
Click to expand...
Click to collapse
Debate my breath? Well, my breath reeks of Marijuana... I think it's a liberal.
Lol
Just a question: since I'll be repopulating all the partitions with the stock blob, does that affect my unlocked bootloader, or is it gonna be straight up manufacturer reset? I'm sure that's covered in the threads that address the 'buster99' process, but I need to go locate the thread. I didn't fully digest the thread as i'd yet to find the blob I could d/l, until you hooked it up. ?

No, you cannot relocate the bootloader. Flash away

berndblb said:
No, you cannot relocate the bootloader. Flash away
Click to expand...
Click to collapse
Ugh, corrupt archive. ? trying to download from a different server this time.
Edit: same results w/new download. Repairing the archive didn't help either.
Asus, ya'll are killing me! Every link on the interweb linking to a TF700 firmware is broken, and all that can be found are for the 700kl.

Final update:
Found a valid download link for 10.6.1.14.8. Had some difficulties with it (revived the post on the buster99 process) -- followed as written, and had a fail on the last process <invalid state>. Being super impatient (mentioned *that* before, lol), I decided to try and reestablish twrp, as that was the original issue. That took! Flashed 3.0.0-1 (iirc), was able to open twrp, but couldn't mount system or anything. So I formatted the crap out of all partitions, converted /data to f2fs, and was able to successfully flash katkiss nougatella. Wiped the caches, rebooted, and I'm golden! 3 months later, and it finally works.
Moral of the story: don't sell rooted devices to ppl who don't understand what that entails. You can tell a person till ur blue in the face, NO FACTORY WIPE VIA ANDROID -- Odds are, they'll forget. Worked out for me in the long run (took back the 700 and gave a 201 as replacement), but i was never sure I'd come out clean on the other end.

I have similar problem, i can't even go to bootloader.
Just keep bootlooping. Is there any chance of reviving my tf700t?
If yes please advice me step by step process to do that.
Thanks

Not enough information. What can you get to?
What's your ROM, bootloader, recovery?

berndblb said:
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
Click to expand...
Click to collapse
Thanks you already help on other thread.
It's a long story how this happened.
By the way I was running nougtell version don't remember as it happened in January.
I wanted to transfer some video files on my usb 2tb hard drive, so I did usb otg connection to my tab, i did this thing before and I use es file explorer to do the transfer, few occasions es file hang or whole tablet hang so I have to restart. But in January when this thing happened it just went into bootlooping i can go to fastboot but not recovery or android.
Then I search on many thread i couldn't find any working solution.
My cable was not detecting tab so I couldn't able to push recovery., But the same cable was ok for charging.
Then I bought new cable from eBay it took around a month to arrive.
But in mean time being impatient i tried data wipe from bootloader.
Then even i couldn't able to bootloader after that.
I know being impatient with doing something like this is not good you have to suffer.
Bootloader was latest version .14 at the end and recovery was 3.0.1
Using nogtella rom
Thanks