Database Develop

[Q] /sigh please need some help with Sprint Tab

Please let me start out by saying that I have two epics and a tab, all sprint. I read and post and donate regularly on the Epic4g forums. I'm not a newb, just someone that is trying to get the most out of his devices.
I have read about 70+ pages over multiple threads including the bible and other stickies, spent several if not tens of hours...and I have to say I'm just lost enough to need to post this.
Please no slams, just help and post your answer, or click to another thread and ignore. Thanks in advance.
1. Trying to get Ext4. It looks like Ext4 is *maybe* doable if you try using a verizon tab flash somewhere, but I dont see enough replies to make me comfortable enough that it works. I have a class10 SD card, similar to what I have in my epic that is all ext4. Any advice ?
2. Trying to apply OTA for Sprint - I am on DJ29 baseband and DJ30 build. Cant get the OTA to work, it goes about 11seconds into the install and then I get triangle with an exclamation next to Mr Android. Reboots automatically, update doesnt apply. I *am* rooted, with z4root. I already went to stock using Privacy, but didnt flash anything.
3. Recovery. So...no CWM for Sprint ? Rom Manager isnt the same thing.....and doesnt have an option for Sprint tab anyways. What is working for the sprint tab?
4. Flashing. Im used to Odin, saw Heimdall (never used that), and dont see any recovery working here for Sprint...so stopped there just in case. Also seen reference to SGS. What is recommended for Sprint users.
5 After I get Ext4 and OTA, would like to try a good combo of Kernel and Rom, preferably overclockable. This is different than the Epic in that there, we just do Rom, and Firmware doesnt seem to be much of an issue - everyone just uses a base of the DK28 hack release or the stock release. Seems there are more firmwares here, mostly not for Sprint.
And to answer the top of the thread poll about *REALLY* liking the idea of a Sprint only subforum....OMFG yes. That would really make a lot of this easier......
Thanks again for the help.....I appreciate it guys.

anyone ? )))

Im also in need of sprint tab help as well, i heard voodoo say that conversion was successful after flashing this http://forum.xda-developers.com/showthread.php?t=941781
however wouldnt boot and got stuck at the Samsung screen (boot loop)
since then i flashed this:
KhasMek.Voodoo.plus.CDMA.Tab.v2.zImage
and this together
KhasMek.DJ11.KleanMod.v2.ext4
still stuck at samsung, and now voodoo says "not enough space on partition" "system not available"
EDIT: i flashed back to sprint stock and all good
EDIT: i flashed KhasMek.Voodoo.plus.CDMA.Tab.v2.zImage again and still getting stuck at samsung after successful voodoo conversion.

Been stuck at the logo for ever think it has something to do with that hidden partition that tries to reinstall all your old apps -_-

This is exactly why I sold my sprint tab and got the t mobile tab. Just not enough support.
Someone got CWM to work on a sprint tab. You will just have to read the thread for that portion.
Good luck w/ getting what you need. It is tough to get stuff for the sprint tab.

jkurl said:
This is exactly why I sold my sprint tab and got the t mobile tab. Just not enough support.
Someone got CWM to work on a sprint tab. You will just have to read the thread for that portion.
Good luck w/ getting what you need. It is tough to get stuff for the sprint tab.
Click to expand...
Click to collapse
Agreed, but now that i got flashing back to rooted stock figured out its a breeze to flash and try stuff, albieit there's not much to flash

Which Sprint stock did u use?? link plz

Okay, you guys that want the ext4 conversion for sprint, why don't you try this, get heimdall all set up, download koush's zImage (last I checked it was a bad link in his thread so I've mirrored it HERE) and perform this command
Code:
heimdall flash --recovery verizon_zImage --kernel verizon_zImage
that should convert you over to ext4 safely and allow you to boot into your system (note, my K-lean ROM probably won't work on sprint tabs, I haven't confirmed myself though). If you can't boot, it will allow you into ROM manager where you can try a factory reset and that should allow you to boot. If you can't convert to ext4 (system giving an error about free space) you should flash the stock kernel via that same method (both --recovery and --kernel) and factory reset. Then flash koush's kernel the way I mention above.
Then, you can safely flash my kernel, but be sure at this point I'm only recommending people to flash via --kernel with my kernel, not --recovery too. This is because my recovery is still not 100% (or even 50%) functional atm (soon, gawds I hope I fix it soon!) and it's nice to have something to fall back on when you need to clear the cache or factory reset. This also causes my kernel to have some issues with the conversion process, which is why sometimes it leaves people at the samsung screen after it claims to have converted properly.

Should be in general
http://forum.xda-developers.com/showpost.php?p=10058503&postcount=1

Boushh said:
Okay, you guys that want the ext4 conversion for sprint, why don't you try this, get heimdall all set up, download koush's zImage (last I checked it was a bad link in his thread so I've mirrored it HERE) and perform this command
Code:
heimdall flash --recovery verizon_zImage --kernel verizon_zImage
that should convert you over to ext4 safely and allow you to boot into your system (note, my K-lean ROM probably won't work on sprint tabs, I haven't confirmed myself though). If you can't boot, it will allow you into ROM manager where you can try a factory reset and that should allow you to boot. If you can't convert to ext4 (system giving an error about free space) you should flash the stock kernel via that same method (both --recovery and --kernel) and factory reset. Then flash koush's kernel the way I mention above.
Then, you can safely flash my kernel, but be sure at this point I'm only recommending people to flash via --kernel with my kernel, not --recovery too. This is because my recovery is still not 100% (or even 50%) functional atm (soon, gawds I hope I fix it soon!) and it's nice to have something to fall back on when you need to clear the cache or factory reset. This also causes my kernel to have some issues with the conversion process, which is why sometimes it leaves people at the samsung screen after it claims to have converted properly.
Click to expand...
Click to collapse
yeah that was a dead end before i think, I'll try what you've suggested, thanks!, right now im getting over 2200 quadrant with stock kernel and zepher Rom and OCLF .. pretty pleased with the results so far, but really want to try your kernel. thanks for your reply
buhler

deathscyte said:
Which Sprint stock did u use?? link plz
Click to expand...
Click to collapse
this has everything you need to flash sprint galaxy tab to stock...
Code:
http://www.ndsico.com/XDA/TAB/Sprint_DJ30_TAB.zip
except the usb drivers which you can find easily.
(just keep in mind that i was setup with the driver Hiemdall uses and had to rollback my driver to the android usb driver to use with Odin. maybe that was just my setup, i dunno..)
EDIT: that link comes from here
Code:
http://forum.xda-developers.com/showthread.php?t=919986

buhlerbuhler said:
yeah that was a dead end before i think, I'll try what you've suggested, thanks!, right now im getting over 2200 quadrant with stock kernel and zepher Rom and OCLF .. pretty pleased with the results so far, but really want to try your kernel. thanks for your reply
buhler
Click to expand...
Click to collapse
Don't flash my kernel with OCLF enabled, OCLF breaks a lot and doesn't produce accurate benchmark tests.

buhlerbuhler said:
this has everything you need to flash sprint galaxy tab to stock...
Code:
http://www.ndsico.com/XDA/TAB/Sprint_DJ30_TAB.zip
except the usb drivers which you can find easily.
(just keep in mind that i was setup with the driver Hiemdall uses and had to rollback my driver to the android usb driver to use with Odin. maybe that was just my setup, i dunno..)
EDIT: that link comes from here
Code:
http://forum.xda-developers.com/showthread.php?t=919986
Click to expand...
Click to collapse
My Tab wont boot still -_-, Im seeing alot of crap in logcat when its trying to boot up, like old appz and games is there anyway to clear that folder, maybe something in there is stopping me from booting?

[MOD][CWM][Bell][Gobstopper] Stock 2.2.2 for Bell Updated 10/01/2011

Disclaimer: You may brick your phone. NOT for AT&T
​
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.​Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!​Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip​

Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!

When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?

Will you eventually be able to compile a zip for Bell gingerbread?

IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.

IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!

i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery

akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)

NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.

raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!

yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.

Awesome work! This makes it much easier to get back to 2.2.2

Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.

This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists

y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.

anyone try flashing the bootloader and radio?

kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!

So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome

y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!

ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.

[Q] Gingerbread update problem 7inch Tab

Hello! I have been researching this for a friend and figured I would try good old XDA. Here is the problem, after a forum search only one post had this problem but with no solution.
It is a bone stock 7 inch galaxy tab. It is running froyo and is prompted to download the gingerbread update. After the download, it will boot and start to flash, approx 1/3 of the way, the patching stops, an exclamation point appears then the tab reboots back to Froyo as the update has failed.
Any idea what is causing this? I have booted it into recovery and wiped data/cache and even SD card for good measure. It always does the same thing.
I am savvy with working on Motorola droids, but samsung is new to me. I did reading and found out about Heimdal and Odin. I believe this must be something like RSDlite that I use but am uncertain.
Anyways, how can i get this update to go through? can I retrieve the file after it downloads, change it to "update.zip" and flash it in recovery? The only thing I can think of is having him download the 2.3.5 Stock + root file from this thread. and flashing this in Heimdal.
What seems to be the best possible action here. Thanks

in99flames said:
Hello! I have been researching this for a friend and figured I would try good old XDA. Here is the problem, after a forum search only one post had this problem but with no solution.
It is a bone stock 7 inch galaxy tab. It is running froyo and is prompted to download the gingerbread update. After the download, it will boot and start to flash, approx 1/3 of the way, the patching stops, an exclamation point appears then the tab reboots back to Froyo as the update has failed.
Any idea what is causing this? I have booted it into recovery and wiped data/cache and even SD card for good measure. It always does the same thing.
I am savvy with working on Motorola droids, but samsung is new to me. I did reading and found out about Heimdal and Odin. I believe this must be something like RSDlite that I use but am uncertain.
Anyways, how can i get this update to go through? can I retrieve the file after it downloads, change it to "update.zip" and flash it in recovery? The only thing I can think of is having him download the 2.3.5 Stock + root file from this thread. and flashing this in Heimdal.
What seems to be the best possible action here. Thanks
Click to expand...
Click to collapse
which model of the tab do you have?

[Q] only boots into recovery

ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.

If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.

drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.

I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.

I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...

drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.

Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.

http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.

Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.

drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.

actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless

Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.

drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.

Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.

oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.

Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again

Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app

I'd try another baseband.

Pic of Dead Droid with ! after firmware update attempt

I recently got my TF701T back from repairs and they of course factory reset it (they put a new battery in). We all know it needs factory reset for that right? Anyways. I do a check for updates and nothing. I know I was running 4.4 previously but updater says no updates and stuck on original. So I start reading and download the latest US 4.4 firmware directly from ASUS, unzip it and put in main directory (verified mine was US) and reboot. Says all is fine, would I like to update, yes, reboot and I get the Android gear guy for about 10 minutes then it reboots. He shows up again and dead android shows up.
Now it just loops forever to this. I spent about 5 hours reading forums here, attempted a restore, but 1. the recovery.img link is bad and 2. my tablet isn't rooted.
Any suggestions? I can access the fastboot screen that gives me "RCK, Android and "Wipe Data". I tried Wipe data 3 times, no good still getting dead guy. I tried copying the latestest zip file to an sd card with boot.img and blob and file and ran RCK and it says match then reboots then dead guy again...
the fastboot screen says "released by: "US_epad-10.14.1.45-20131014" which I believe is the original.

You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!

So, I had downloaded 3 different versions multiple times before with zero success. But, once I took one and renamed it to T4_SDUPDATE.zip bam!
You just so made my day!
Thank you! Thank you! Thank you!
Devan

I have a question along these lines. What is the difference between the software update and firmware update and when do you do each? I understand the difference between what they are I suppose just not sure if updating is the same. Should I update kernel too or is that updated in an SW or FW update?
Thanks

Anyone?

I have seen these terms used very differently on different device forums.
Here on the Asus tablet forums people mostly talk about firmware when they mean the whole stock package. The stock firmware always comes with everything: Bootloader, recovery, rom and kernel
On the HTC M8 forum for example, they make a clear distinction: Software is rom and kernel, firmware is bootloader, radios, baseband etc.
The recovery seems to fall somewhere in between
Your bootloader version determines everything else. You should only flash a recovery, kernel or rom compatible with that particular bootloader.
You can, or have to, update it if you want to run a rom that requires a later or newer bootloader. Asus encrypts their BLs, so bootloader updates can only come from them - so far only with the release of a new version of the OEM "firmware".
If you as an unlocked, custom rom'd user then want to install a rom based on that new firmware, you have to update the bootloader and possibly but not necessarily your recovery before flashing the new custom rom.
Custom recoveries get more frequent updates. CWM, TWRP or some enterprising dev release new versions every few months. Always make sure it is compatible with your bootloader and rom. In most cases you can easily skip a few versions. But if you update your rom, let's say, from JB to Lollipop you should also update your recovery.
The kernel is considered to be part of the rom. At least every rom I know of comes with a kernel, some even with several to choose from. And it is a popular sport to try the same rom with different kernels.
You update the rom whenever the developer releases a new, updated version - or not if you're happy with what you got.
The safest place to be is always up-to-date: The latest roms usually require the latest bootloader and it's best to run both with the latest recovery.
If you have a working combo you can stick with it for years if you like.
But if you've been away for a while, did not follow the latest development, and want to update, you always have to:
Check if your bootloader is still current. If not, update it
Update your recovery
Wipe data, cache and Dalvik
Flash the new rom.

Nice explanation, I knew all of this but there is no way I could have explained it.

berndblb said:
You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!
Click to expand...
Click to collapse
THANK YOU!!!! IT worked like a miracle... Thank you !!!! :good::good::good: