[Q] Lost WIFI after flashing/recovery - Sony Ericsson Xperia Neo, Pro

Hi all!
My wifi is not working at all on my xperia neo mt15i. In wi-fi settings it just says "Error". Trying to enable wifi: "Turning on ..." flashes by and then "Error".
Here is the story:
It used to work of course. Until yesterday. A few days ago I reverted from 4.0.2.A.0.62 to 4.0.2.A.43 (?) and rooted it. Then I upgraded to 62 OTA. This was of course to get root. No problems here, wifi working.
Then, yesterday I wanted to test ICS. So I unlocked the bootloader with instructions from sonyericsson using fastboot in linux. Went smooth and I confirmed the unlock. Flashed an ICS kernel with fastboot. Went into recovery, wiped all, did an update with a zip, rebooted. But here I got stuck on SONY logo at boot.
So I went into CWM recovery and did a recovery to the backup I made before unlocking bootloader. After booting everything looked good, but I did not check wifi. Went to sleep and this morning I realized that I had lost wifi. Could not get it to work at all.
So I tried once more to do recovery of same backup. This time I wiped caches, factory reset and wiped dalvik-cache before recover backup. After boot, same problem with wifi.
So, what do I do now? I have searched forums but have no clue. Please help!

I had a look in logcat and found this:
E/WifiService( 268): Failed to load Wi-Fi driver.
Is there a mismatch between kernel and wifi-driver? How come, since I did a recovery I would suppose both kernel and all drivers would be recovered and match?

Which ICS you used, since you say you flashed zip? And stock one is in img.
Is it possible that you didn't wipe system partition before flashing zip? I made same mistake yesterday, and got to stuck on sony screen Even though I didn't move to some different rom, but the same, so it's strange, but never mind.
Then you say you went back to your backup(.62 ?), did you also flash your old kernel?
So what kernel do you have now on your phone? Stock?
---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------
yogodo said:
I would suppose both kernel and all drivers would be recovered and match?
Click to expand...
Click to collapse
Ah, there's problem kernel isn't contained in backup made from CWM. You need to flash it trough fastboot.

Madfysh said:
Which ICS you used, since you say you flashed zip? And stock one is in img.
Is it possible that you didn't wipe system partition before flashing zip? I made same mistake yesterday, and got to stuck on sony screen Even though I didn't move to some different rom, but the same, so it's strange, but never mind.
Then you say you went back to your backup(.62 ?), did you also flash your old kernel?
So what kernel do you have now on your phone? Stock?
---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------
Ah, there's problem kernel isn't contained in backup made from CWM. You need to flash it trough fastboot.
Click to expand...
Click to collapse
First I followed this guide: http://forum.xda-developers.com/showthread.php?t=1468866, to get root and then go to 4.0.2.A.0.62.
Then for ICS I followed this guide: http://forum.xda-developers.com/showthread.php?t=1517794.
So the nandroid backup does not contain the kernel. I will try to flash kernel from 4.0.2.A.0.62 since it would match my backup. I hope
Thank you Madfysh for your help.
I will come back here later this evening or so and report the result.
Cheers!

Yup, I'm using same ROM now. Most likely you forgot to wipe/format something, as I did yesterday
Strange is that before I flashed that zip I was already on that ROM, so not sure why not wiping system partition confused it, but..

Maybe I will try ICS again first. Making sure I wipe everything.
But as I recall I think I followed the instructions.
1) I flashed the ICS kernel
2) Boot to CWM and wiped all I could wipe in the menues, even advanced/wipe dalvik-cache, and factory reset or whatever. Instruction says "format system, format data, format cache". I can't find that in CWM menues though. Is THAT my problem (with ICS)?
3) Flash update zip and reboot. Here it got stuck on SONY logo. Waited at least 15 minutes.
So maybe there is something I missed to format/wipe/clean?
By the way: if I now look at kernel version it says 2.6.32.9-perf which I think is the kernel from 4.0.2.A.0.62. So it did recover that from the backup? No?

yogodo said:
Instruction says "format system, format data, format cache". I can't find that in CWM menues though. Is THAT my problem (with ICS)?
Click to expand...
Click to collapse
Yup, there's your problem
My phone is on charger now so I can't check to be 100% sure, but I think those options are under mount and storage.
yogodo said:
By the way: if I now look at kernel version it says 2.6.32.9-perf which I think is the kernel from 4.0.2.A.0.62. So it did recover that from the backup? No?
Click to expand...
Click to collapse
No. It's just Sony didn't change kernel version.
That doesn't mean you can use kernel for GB on ICS and vice versa.

Madfysh said:
Yup, there's your problem
..., but I think those options are under mount and storage.
Click to expand...
Click to collapse
Sir! You are absolutely correct! I just booted to CWM and there they are!
Madfysh said:
No. It's just Sony didn't change kernel version.
That doesn't mean you can use kernel for GB on ICS and vice versa.
Click to expand...
Click to collapse
OK, thank you!
And thank you again
To night I WILL try ICS again, wiping even more!
Cheers!

I realized I had everything I needed at hands: ICS kernel, ICS update. Go for it!
So I rebooted to CWM and did all wiping and formatting. Then update with zip, reboot. And now I've got ICS! Nice! Everything thing seems to work alright, awesome!
Problem solved then.

Glad we solved that
Enjoy in ICS.

But you got it working in ICS. Same is happening for me. Its working in ICS but not on GB.
I am on Droid 3 which has locked bootloader & I have read that Locked bootloader = NO Kernel Replacement. Hence facing same wifi issue.

kapilthio said:
But you got it working in ICS. Same is happening for me. Its working in ICS but not on GB.
I am on Droid 3 which has locked bootloader & I have read that Locked bootloader = NO Kernel Replacement. Hence facing same wifi issue.
Click to expand...
Click to collapse
Oh yes, I've got it working. The problem was that I mistakenly had the wrong kernel. I went from GB to ICS switching kernel and everything. Then I tried to go back to GB but I did not switch back the old kernel.
I actually never tried again to go back to GB since I got it working in ICS. But I suppose it would work in GB if I switch kernel and install my recovery backup.
Good luck!

kapilthio said:
But you got it working in ICS. Same is happening for me. Its working in ICS but not on GB.
I am on Droid 3 which has locked bootloader & I have read that Locked bootloader = NO Kernel Replacement. Hence facing same wifi issue.
Click to expand...
Click to collapse
Droid phones are different and can flash kernel &devtree from recovery.
Sent from my MT11i using Tapatalk

Related

[Q] Gtab wont take roms that arent NVflashed

So, i had my gtab working fine then i tried to go to BL 1.2, had a rom running for a while then decided i wanted to go back to a 1.1 rom, I nvflashed to 1.1 stock image and now my tablet wont boot on any rom that isnt NVflashed, regardless of if i use CWM or stock recovery, what am i doing wrong? It only runs stock Viewsonic roms
What rom were you trying to flash that you could only use on 1.1 that there isn't a port running for 1.2.?
Let me guess. You never wiped out your data before you flash a new rom.
This is a common mistake made by beginners. Is this the case?
goodintentions said:
Let me guess. You never wiped out your data before you flash a new rom.
This is a common mistake made by beginners. Is this the case?
Click to expand...
Click to collapse
No, this is not the case, i am aware that NVflashing changes partition sizes, is it possible that customs roms are larger than Viewsonics rom and there isnt sufficient space to load a custom rom?
Mantara said:
What rom were you trying to flash that you could only use on 1.1 that there isn't a port running for 1.2.?
Click to expand...
Click to collapse
I was running BOS on 1.2 but i was having isues where if the tablet was powered off after initial boot it would not booot again so i wanted to run the 1.1 honeycomb
Have you used cwm to repartition and then load a rom?
Mantara said:
Have you used cwm to repartition and then load a rom?
Click to expand...
Click to collapse
Yes, but from what i know you can only partition the internal SD from CWM
Did you update using ota from stock brfore trying to flash another rom?
How about this. What version of nvflash are you using? I don't just mean 1.1 or 1.2. I'm talking about the long string of number in the nvflash zip file.
There are some nvflash versions floating out there that are bad.
Try this. Go to my website at
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Use the code red procedure. Don't use anything you already have. Download everything from my website. Follow the procedure I outlined. See if this changes anything.
goodintentions said:
How about this. What version of nvflash are you using? I don't just mean 1.1 or 1.2. I'm talking about the long string of number in the nvflash zip file.
There are some nvflash versions floating out there that are bad.
Try this. Go to my website at
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Use the code red procedure. Don't use anything you already have. Download everything from my website. Follow the procedure I outlined. See if this changes anything.
Click to expand...
Click to collapse
my NVflash is not the same extention but the 1.1 file has the same extention as yours, ill try to flash yours anyways.
Mantara said:
Did you update using ota from stock brfore trying to flash another rom?
Click to expand...
Click to collapse
Ive tried ota and NVflash to 1.1 directly neither work
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Was written for linux you might need to adjust the nvflash commands for windows.
Thanks all of you, I got it to run BOS on 1.2 using goodintentions' NVflash, idk what happened but it appears to be working weirdly though, it wont boot a second time without a factory data reset
whodatxevg said:
Thanks all of you, I got it to run BOS on 1.2 using goodintentions' NVflash, idk what happened but it appears to be working weirdly though, it wont boot without a factory data reset
Click to expand...
Click to collapse
Didn't I tell you to use code red on my start here page? Part of the instructions in code red is to wipe data/factory reset.
You didn't really read my code red did you?
goodintentions said:
Didn't I tell you to use code red on my start here page? Part of the instructions in code red is to wipe data/factory reset.
You didn't really read my code red did you?
Click to expand...
Click to collapse
It wont boot without a data reset AFTER the initial boot. I dont think its normal to have to do a data reset after a rom is already installed but that seems to be a rom issue
Yep. Rom issue. Bos needs to be factory reset after flash. Its odd but what needs to happen to boot initially.
Glad to see you got her up and running
Mantara said:
Yep. Rom issue. Bos needs to be factory reset after flash. Its odd but what needs to happen to boot initially.
Click to expand...
Click to collapse
Oh well, thats why its not a final build.
Thanks again guys.
I suggest that all HC roms have a boot splash screen that simply states "This is an Alpha build, please on't expect everything to work like you want it to"
People keep having these delusions that the HC roms will work perfectly...
whodatxevg said:
It wont boot without a data reset AFTER the initial boot. I dont think its normal to have to do a data reset after a rom is already installed but that seems to be a rom issue
Click to expand...
Click to collapse
No it's not a rom issue.
As I explained on my website, the problem is that nvflash DOES NOT wipe out your data. When you nvflash a new stock rom, the data from the previous rom is still there. Some are not compatible with the stock rom, so the left over data cause an interruption in the normal boot process. Sometimes, it bootloops. Sometimes, you are kicked into permanent apx mode.
That's why in my code red procedure I told you to wipe data/factory reset RIGHT AFTER you nvflash.
There's a purpose to the way I ordered my instructions.
Better read the instructions better next time. Could have saved you hours of frustration.
And yes, it is normal to wipe data before you flash a new rom. Since nvflash doesn't wipe data, you have to wipe data manually after you nvflash. It's the same as wiping data before you flash the stock rom.
There have been cases with bos where full wipes were done (as far as were stated in the posts but we know no one ever lies right?) and it would bootloop untilled full wipes were done again. Who knows.
Personally I wipe and repartition every time I flash a new rom. If its an update I leave it, if its a new rom I start from a clean slate. I use titanium backup almost daily and have copies of my recovery backup on my PC weekly. Its slightly time consuming but unborking takes a hell of a lot longer than being extra cautious when flashing

"Downgrade ICS to GB for APN Fix ?"

Here we go...new thread we can use, and hopefully get you back up and running soon..
Let me know when you get here...g
ok yes I have odin 3, and yes i updated drivers last night so we are good to go
okay.... excellent..stand by...I'm going to link and build the files you'll need...g
gregsarg said:
okay.... excellent..stand by...I'm going to link and build the files you'll need...g
Click to expand...
Click to collapse
ok sounds good.. thank you soo much
Jblakeley said:
ok sounds good.. thank you soo much
Click to expand...
Click to collapse
Before we go any further.....you are stock ICS ? using the 3.0.8 stock ICS kernel ?
We should try something else before the downgrade....as you "technically" have the wrong baseband version for TMO...
We need to get you rooted again, and flash up a new radio....first...to test network...
now I know the blaze radio got you stuck, but believe it or not...you need it to run the ATT note, on the TMO network...
Are you familiar with the ICS root process ?
It's too easy...simply push CWM .tar file to the device via Odin, then we can flash the baseband and test.....
quite possibly eliminating the need for much more work...g
gregsarg said:
Before we go any further.....you are stock ICS ? using the 3.0.8 stock ICS kernel ?
We should try something else before the downgrade....as you "technically" have the wrong baseband version for TMO...
We need to get you rooted again, and flash up a new radio....first...to test network...
now I know the blaze radio got you stuck, but believe it or not...you need it to run the ATT note, on the TMO network...
Are you familiar with the ICS root process ?
It's too easy...simply push CWM .tar file to the device via Odin, then we can flash the baseband and test.....
quite possibly eliminating the need for much more work...g
Click to expand...
Click to collapse
yes i do and already have the files saved to the sd card as we tried this process last night to no avail.. i flashed cwm through odin last night and then tried all 3 ics tmo radios.. nothing worked..
Jblakeley said:
yes i do and already have the files saved to the sd card as we tried this process last night to no avail.. i flashed cwm through odin last night and then tried all 3 ics tmo radios.. nothing worked..
Click to expand...
Click to collapse
Okay then...
lets back door the phone.....with the GB.....http://forum.xda-developers.com/showthread.php?t=1506330
stand by...g
Edit:
here is the stock.tar for GB....
You must first...(required by me...LOL) wipe data, and factory reset the device....
Then, push this GB .tar image to your phone via Odin...
Just to clarify: you do this at your own risk....as this image will force restore the device to a stock ATT I717 GB rom.....
let me know when you are done with the flash...then we do step 2....g
Edit: 2....it is wise to format the emmc partition prior to using this method, to clean the ICS files from the device...this is done in CWM....it's not required...but helps...IMHO
gregsarg said:
Okay then...
lets back door the phone.....with the GB.....http://forum.xda-developers.com/showthread.php?t=1506330
stand by...g
Edit:
here is the stock.tar for GB....
You must first...(required by me...LOL) wipe data, and factory reset the device....
Then, push this GB .tar image to your phone via Odin...
Just to clarify: you do this at your own risk....as this image will force restore the device to a stock ATT I717 GB rom.....
let me know when you are done with the flash...then we do step 2....g
Edit: 2....it is wise to format the emmc partition prior to using this method, to clean the ICS files from the device...this is done in CWM....it's not required...but helps...IMHO
Click to expand...
Click to collapse
ok, how do you wipe data and factory reset without root.. is it factory data reset? and how to format emmc?
Just factory reset....if you dont have root,,,you cant format the emmc...
It'll do....
we'll full wipe after you get GB flashed....g
Okay...once you get GB pushed over...
then you need the CWM recovery....
Push it after you push the GB rom. but remember...you must allow the device to reboot after each flash, and then return to download mode again..
It's slow...but it's required....
After you get CWM pushed.....and booted, then we will go into CWM and do some house keeping on the EMMC....
followed by this:
http://www.4shared.com/zip/0zahxvtc/033112.html?
That is the radio image we are going to flash in CWM...and if we get lucky, It's gonna fix this mess for you....
I'll wait here....tap, tap, tap, tap.......LOL....g
ok flashed it..
android version: 2.3.6
bb version: i717uclf6
kernel version:2.6.35.11
build #: gingerbread.ucla1
---------- Post added at 01:37 PM ---------- Previous post was at 01:32 PM ----------
ok 2.3.6 installed and cwm flashed.. now what lol
Okay......now we need the CWM recovery....
so back into download mode, and Odin push this:http://forum.xda-developers.com/showthread.php?t=1526431
It's the top recovery on the first page...just click the "odin" version, and it will download the correct CWM.tar image...then flash that sucker....g
edit: yur fast...LOL
Now, we need to boot into CWM.....
then, wipe data, factory reset.......
then wipe cache, dalvik cache, battery stats....
then...and here is the scary part...
In the advanced menu options, you will find the option to format "EMMC"....do it...then reboot from the CWM screen.....g
After the EMMC wipe and reboot....you are going to flash this radio image in CWM...
Sorry for the reboot, but it was needed to flush the memory, and repopulate the Emmc with only the rom specific data needed to boot....http://www.4shared.com/zip/0zahxvtc/033112.html?
ok im in advanced menu.. there is no format emmc option
reboot recovery
wipe dalvik
wipe battery
report error
key test
show log
partition sd card
fix permission
go back
Jblakeley said:
ok im in advanced menu.. there is no format emmc option
reboot recovery
wipe dalvik
wipe battery
report error
key test
show log
partition sd card
fix permission
go back
Click to expand...
Click to collapse
Okay...you have a different CWM version...thats okay...lets flash the radio image in CWM, and see if you get service...
this radio is a base TMO image, no frills, but is compatible with your network...and if service is available, you'll get it after the flash and reboot...
http://www.4shared.com/zip/0zahxvtc/033112.html?
tense drama, lads!
Ok. I felt the need to chime in here. G, you are going above and beyond and just wanted to say thank you for all those folks who need help! Although XDA isn't a help hotline, it's people like you that help spread the fun and excitement in the mobile electronics realm. I do what I can but you sir are taking it to another level. I know there's more like you but since I've followed this from the beginning, you get my thanks!
Glad you're here.
Sent from my SGH-I717 using xda app-developers app
rangercaptain said:
tense drama, lads!
Click to expand...
Click to collapse
i'm gonna stroke out...LOL:laugh:
dakleenupman said:
Ok. I felt the need to chime in here. G, you are going above and beyond and just wanted to say thank you for all those folks who need help! Although XDA isn't a help hotline, it's people like you that help spread the fun and excitement in the mobile electronics realm. I do what I can but you sir are taking it to another level. I know there's more like you but since I've followed this from the beginning, you get my thanks!
Glad you're here.
Sent from my SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
It's what I do......:good:
Many thanks for the kind words....g
gregsarg said:
Okay...you have a different CWM version...thats okay...lets flash the radio image in CWM, and see if you get service...
this radio is a base TMO image, no frills, but is compatible with your network...and if service is available, you'll get it after the flash and reboot...
http://www.4shared.com/zip/0zahxvtc/033112.html?
Click to expand...
Click to collapse
Negative ghost rider ... No SIM Emergency Calls Only...

Boot Loop Problems Help please

Hello guys,
I have a problems, ive Flash my Sam-T859 and it seemed to work fine for almost a month but a few hours ago i was playing a Game (Contract Killer 2) and it just crashed and started doing the boot loop thing.
Ive Been on google all day non stop following instructions that lead to dead ends.
Ive used Odin3_v1.85 and did the "PDA" thing and it passed but went right back into the boot loop.
i read somewhere that a guy had the same problem i did but somehow figured it out. He wasnt sure how he fixed it but he said he thought it was because he needed a legit .Tar file so if someone could direct me to that would be most appreciated.
Sam T859 Galaxy Tab 10.1
Dayquan94 said:
Hello guys,
I have a problems, ive Flash my Sam-T859 and it seemed to work fine for almost a month but a few hours ago i was playing a Game (Contract Killer 2) and it just crashed and started doing the boot loop thing.
Ive Been on google all day non stop following instructions that lead to dead ends.
Ive used Odin3_v1.85 and did the "PDA" thing and it passed but went right back into the boot loop.
i read somewhere that a guy had the same problem i did but somehow figured it out. He wasnt sure how he fixed it but he said he thought it was because he needed a legit .Tar file so if someone could direct me to that would be most appreciated.
Sam T859 Galaxy Tab 10.1
Click to expand...
Click to collapse
if you are rooted....
...boot into recovery and wipe data,cache,dalvik cache ( dalvik is under advanced )...now reboot.
if you are not rooted...
...boot to stock recovery and wipe cache..reboot. If that doesnt work. Then i would go to sammobile .com and find the original firmware that your device came with and i would odin that...if that doesnt work. Then you are going to need a pit.file and use odin but you will repartition the sdcard this time.
google what ive told you here so you have a better understanding of what im saying.....and let me know.
good luck
Gil81 said:
if you are rooted....
...boot into recovery and wipe data,cache,dalvik cache ( dalvik is under advanced )...now reboot.
if you are not rooted...
...boot to stock recovery and wipe cache..reboot. If that doesnt work. Then i would go to sammobile .com and find the original firmware that your device came with and i would odin that...if that doesnt work. Then you are going to need a pit.file and use odin but you will repartition the sdcard this time.
google what ive told you here so you have a better understanding of what im saying.....and let me know.
good luck
Click to expand...
Click to collapse
i am rooted and when i tried that i received this
"E: unknown volume for path [/sd-ext] and when i i click yes it freezes rebootes then goes back to the loop
Dayquan94 said:
i am rooted and when i tried that i received this
"E: unknown volume for path [/sd-ext] and when i i click yes it freezes rebootes then goes back to the loop
Click to expand...
Click to collapse
alright...i think you have some corrupted data on the sdcard....i had this happen to me twice.
see if you can just wipe data...
... if you cant..then go into mounts and mount/format data..if you get really desperate you can format the sdcard from here...,but i would flash a rom first..the one you were running..that way you have an os to boot to..unless you have easy access to odin and a pc...inwhich case id wipe it and odin the original firmware and root all over again ...
keep me posted on the situation
Gil81 said:
alright...i think you have some corrupted data on the sdcard....i had this happen to me twice.
see if you can just wipe data...
... if you cant..then go into mounts and mount/format data..if you get really desperate you can format the sdcard from here...,but i would flash a rom first..the one you were running..that way you have an os to boot to..unless you have easy access to odin and a pc...inwhich case id wipe it and odin the original firmware and root all over again ...
keep me posted on the situation
Click to expand...
Click to collapse
ok im on a PC now can you tell me what to do exactly ., and i tried to mount/format but it just went back into the boot loop
Dayquan94 said:
ok im on a PC now can you tell me what to do exactly ., and i tried to mount/format but it just went back into the boot loop
Click to expand...
Click to collapse
you need to find the original firmware for your device and flash it in the pda slot in odin...let me look for a guide for your device to make sure....
im at work so it might take a minute..
Gil81 said:
you need to find the original firmware for your device and flash it in the pda slot in odin...let me look for a guide for your device to make sure....
im at work so it might take a minute..
Click to expand...
Click to collapse
No rush take your time thanks a lot for this by the way
Dayquan94 said:
ok im on a PC now can you tell me what to do exactly ., and i tried to mount/format but it just went back into the boot loop
Click to expand...
Click to collapse
to make so im sure.....you havent been able to wipe the sdcard...data...cache...dalvik..
and also...have you tried to mount sdcard then do your wipes( data,cache,dalvik )and flash a rom..
Gil81 said:
to make so im sure.....you havent been able to wipe the sdcard...data...cache...dalvik..
and also...have you tried to mount sdcard then do your wipes( data,cache,dalvik )and flash a rom..
Click to expand...
Click to collapse
So far I've only been able to wipe cache
Dayquan94 said:
So far I've only been able to wipe cache
Click to expand...
Click to collapse
also...did you try to flash a new version of cwm recovery...i see droidbasement has one built specifically for your device....i believe im correct in that you have the t-mobile variant of the 10.1 galaxy tab...could you also tell me if it is a wifi only variant or does it have a sim card...im assuming it has a sim card,being that it is a t-mobile variant...but assumptions in this kind of ( work..lol ) can lead to getting a new coaster..lol
Gil81 said:
also...did you try to flash a new version of cwm recovery...i see droidbasement has one built specifically for your device....i believe im correct in that you have the t-mobile variant of the 10.1 galaxy tab...could you also tell me if it is a wifi only variant or does it have a sim card...im assuming it has a sim card,being that it is a t-mobile variant...but assumptions in this kind of ( work..lol ) can lead to getting a new coaster..lol
Click to expand...
Click to collapse
Yes it is tmobile And it does has a SIM card
Dayquan94 said:
Yes it is tmobile And it does has a SIM card
Click to expand...
Click to collapse
ok...now were cookin..lol
im also assuming it has a seperate kernal and recovery partition....like my p7510 wifi only variant..
if this is correct...i would either use odin to flash a newer recovery or adb to push the recovery zip file to the device..if you push the zip..just flash it..then reboot recovery and try to do your wipes and flash a rom..
this is a long shot...but im baving trouble finding the original firmware tar..if this doesnt work...i would say our next step would be to flash a kernel in recovery or odin..then flash a rom that is compatible with the kernel..i know this sounds like its redundit....but im thinking your recovery or kernel might be clashing..if not seen it before on this device...but i have seen it on other devices..
---------- Post added at 02:14 PM ---------- Previous post was at 02:09 PM ----------
@Dayquan94
ok...i have a meeting at 2:30...should be over by 4 or 4:30...
ill get back with ya...sorry for the wait...real life is can be a pain...lol
Dayquan94 said:
Yes it is tmobile And it does has a SIM card
Click to expand...
Click to collapse
ok...im back on today....
so run down what your situation again, so i know where you stand....the more info the better...everything is relavent..
Gil81 said:
ok...im back on today....
so run down what your situation again, so i know where you stand....the more info the better...everything is relavent..
Click to expand...
Click to collapse
ok sorry., ive been out of town without access to a computer
Gil81 said:
also...did you try to flash a new version of cwm recovery...i see droidbasement has one built specifically for your device....i believe im correct in that you have the t-mobile variant of the 10.1 galaxy tab...could you also tell me if it is a wifi only variant or does it have a sim card...im assuming it has a sim card,being that it is a t-mobile variant...but assumptions in this kind of ( work..lol ) can lead to getting a new coaster..lol
Click to expand...
Click to collapse
Im really not sure what im doing so im hoping you could link me to the correct programs/Software i need
Dayquan94 said:
Im really not sure what im doing so im hoping you could link me to the correct programs/Software i need
Click to expand...
Click to collapse
well buddy...after reading back through your post...i think you flashed something wrong with odin....but since you have odin mode/download mode and recovery still available...
i think we need to flash a recoveryl with odin....go to droidbasement and download that recovery tar...follow the instruction and flash it with odin,making sure only what is said to be checked in odin is checked.
next....use your pc to push a rom to your device...
boot recovery and wipe data...cache...dalvik cache(under advanced) and format system(under advanced)...then flash rom and gapps...reboot...enjoy
let me know if you cant google what you need and ill link you to the recovery....but im rooting and installing a rom on my buddies new note 3 and its crazy new to me....so im busy...but ill keep checking my notifications about every 20 minutes if you post something...
Gil81 said:
well buddy...after reading back through your post...i think you flashed something wrong with odin....but since you have odin mode/download mode and recovery still available...
i think we need to flash a recoveryl with odin....go to droidbasement and download that recovery tar...follow the instruction and flash it with odin,making sure only what is said to be checked in odin is checked.
next....use your pc to push a rom to your device...
boot recovery and wipe data...cache...dalvik cache(under advanced) and format system(under advanced)...then flash rom and gapps...reboot...enjoy
let me know if you cant google what you need and ill link you to the recovery....but im rooting and installing a rom on my buddies new note 3 and its crazy new to me....so im busy...but ill keep checking my notifications about every 20 minutes if you post something...
Click to expand...
Click to collapse
alright 1 more question, could you recommend me a ROM to use?
Dayquan94 said:
alright 1 more question, could you recommend me a ROM to use?
Click to expand...
Click to collapse
i prefer the rom in my sig...but any rom kasper_h builds is smooth...but he is only really developing omni rom at the moment and probably the future...the ganboro rom is nice...but it lacks some of the customization i like in a rom...that said,omni rom also lacks the customization i like. but remember...the less resources a rom pulls...the smoother it generally is. so really you just need to read the rom threads and see what fits your taste...
fyi...ive rooted my budddies note3 and a recovery...with a rom soon to follow. so ill keep checking back in about every 10 minutes or so...if you need help...we'll get ya back up tonight..
---------- Post added at 11:57 PM ---------- Previous post was at 11:33 PM ----------
Dayquan94 said:
alright 1 more question, could you recommend me a ROM to use?
Click to expand...
Click to collapse
hey...i said format system is under advanced...but it might be under ( mounts )...been a while since i ran cwm recovery...i use twrp.
sorry about the mis- information...
Gil81 said:
i prefer the rom in my sig...but any rom kasper_h builds is smooth...but he is only really developing omni rom at the moment and probably the future...the ganboro rom is nice...but it lacks some of the customization i like in a rom...that said,omni rom also lacks the customization i like. but remember...the less resources a rom pulls...the smoother it generally is. so really you just need to read the rom threads and see what fits your taste...
fyi...ive rooted my budddies note3 and a recovery...with a rom soon to follow. so ill keep checking back in about every 10 minutes or so...if you need help...we'll get ya back up tonight..
---------- Post added at 11:57 PM ---------- Previous post was at 11:33 PM ----------
hey...i said format system is under advanced...but it might be under ( mounts )...been a while since i ran cwm recovery...i use twrp.
sorry about the mis- information...
Click to expand...
Click to collapse
im trying to format Data but i think its frozen o.0?
Dayquan94 said:
im trying to format Data but i think its frozen o.0?
Click to expand...
Click to collapse
and when i tried to wipe dalvik cache it says E: unknown vloume for path [/sd-ext]
i dont belive ill ever get this working again...

Cant flash ROM; phone stuck

Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
tried flashing another rom?
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
Delete some apps or unwanted ringtones from the rom zip then flash the rom..
try to use newest Milestone from SOKP, where is the file saved, on sd-card or internal memory ?
Make sure the ROM zip is completely downloaded/ copies to ur SD card .. An incomplete zip is a common cause of this error, also make sure u're on the latest version of whatever recovery u're using
Sent from my GT-I9300
Thank you guys for your help. yes jinayhvora I used the newer recovery and it worked like a charm.
However latest is not always better as last time while installing DN3 I couldnt get past the terms and condition. Then I downgraded to a previous version of philz recovery and it worked.
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
:good::good:
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
Yes I agree; can you help me with the below problem though?
anmolgoel said:
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
Click to expand...
Click to collapse
anmolgoel said:
I re-flashed the stock firmware and took its backup; same problem.
Click to expand...
Click to collapse
what do you mean by this?
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
kermage said:
what do you mean by this?
Click to expand...
Click to collapse
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
kermage said:
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Click to expand...
Click to collapse
maybe
anmolgoel said:
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
maybe
Click to expand...
Click to collapse
well, take a new backup now and try if it works..then we can conclude..
I'm curious as to why you aren't using TWRP.
kermage said:
well, take a new backup now and try if it works..then we can conclude..
Click to expand...
Click to collapse
I'm not able to make out whether you're messing with me
the current rom (SOKP) is able to be restored; only problem with the stock rom.
es0tericcha0s said:
I'm curious as to why you aren't using TWRP.
Click to expand...
Click to collapse
because the backup was made in philz. From what I know, CWM and TWRP have different kind of backup files which cant be restored by the other.. let me know if I'm wrong..
Should I use TWRP to backup now.. You think it'll work better than philz?
es0tericcha0s said:
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
Click to expand...
Click to collapse
sorry didnt see this post earlier.. I'm on philz, DN3 is ditto note 3 rom that I was using; it is stock based.
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
es0tericcha0s said:
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
Click to expand...
Click to collapse
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
anmolgoel said:
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
Click to expand...
Click to collapse
Ah. Never used the Online Nandroid one. Never saw the point and trust the actual recovery to be able to backup better. Less chance of issues.

Phone reboots and is stuck in a bootloop afterwards no matter what rom/kernel.

I'm left clueless here. I just can't get it to boot, no matter what ROM/Kernel i'd flash. It was originally running OOS 2.3.1 but flashing it now won't work anymore. It worked briefly for 1 hour with that AOSP 8.1 but then after trying to flash gapps it stuck again in a bootloop. Sometimes it also freezes and reboots while i am flashing sometimes. I really have no idea what should i do next, hope you can help me.
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Kéno40 said:
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Click to expand...
Click to collapse
I updated the bootloader like over a year ago or so. I also tried 2 different versions of TWRP, now i am using the latest one.
ALSO, very sorry it actually is OOS 3.1.4, not 2.3.1, i just typed briefly what i could remember, i haven't been using this phone for months now but i would like to give it to a relative so there's that. Hope you can help me out, i have no clue why is it acting up like that.
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Try to flash official ROM after having wiped everything
Kéno40 said:
Try to flash official ROM after having wiped everything
Click to expand...
Click to collapse
That's what i first tried, mentioned it in the main post.
yayakuya said:
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Click to expand...
Click to collapse
I don't know what to make of this, thought maybe anyone else encountered this problem and has a clue.
gabytzu338 said:
That's what i first tried, mentioned it in the main post.
Click to expand...
Click to collapse
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Kéno40 said:
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Click to expand...
Click to collapse
I don't really understand what you are trying to say. I did wipe everything and the only way to flash anything is through adb sideload anyway since the device is not recognized as storage while in TWRP. I think I am gonna give up on it, I was gonna sell it but I can't risk having it act up days/weeks after i sold it.

Categories

Resources