Erase firmware from stock recovery - Upgrading, Modifying and Unlocking

Hello, I am about to try something strange.
My Tablet VF 1497 won't boot up anymore. I can still get into recovery, but there is no firmware available for flashing.
Now I've found a tool from Alcatel, Mobile Upgrade Q, that flashes the latest stock firmware on the device. It works fine until software version check, then stops saying latest firmware already installed.
So my idea is to mess up the firmware on purpus, to get Mobile Upgrade Q working. But I have no idea how to "destroy" the installed firmware.
Any help is highly appreciated.

tkuemmel said:
Hello, I am about to try something strange.
My Tablet VF 1497 won't boot up anymore. I can still get into recovery, but there is no firmware available for flashing.
Now I've found a tool from Alcatel, Mobile Upgrade Q, that flashes the latest stock firmware on the device. It works fine until software version check, then stops saying latest firmware already installed.
So my idea is to mess up the firmware on purpus, to get Mobile Upgrade Q working. But I have no idea how to "destroy" the installed firmware.
Any help is highly appreciated.
Click to expand...
Click to collapse
Just because the device won't boot up into the firmware doesn't mean that its missing.
Boot into recovery and you should locate an option to restore to factory defaults.
The recovery of a device always has the factory firmware for restoring a devices firmware. Only on a few occasions this cannot be done that depends on what was done by the individual.
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**

Hello Ibuprophen, thanks for the answer.
Unfortunally factory reset doesn't change anything, I should have mentioned.
All the other options, clearing cashes and stuff, don't work either.

tkuemmel said:
Hello Ibuprophen, thanks for the answer.
Unfortunally factory reset doesn't change anything, I should have mentioned.
All the other options, clearing cashes and stuff, don't work either.
Click to expand...
Click to collapse
You may have to go to the forum.vidafone.uk
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**

Thank you, but I have done all this. It appears like a lot of users have the same problem, no solution until now.
May be there is a little chance 4pda.ru, but I need a better translation.
Before the bootloop I dumped the original system, boot and recovery, but I'm not able to make a flashable zip of it. May be this would still be a better chance to bring the tablet back to life...

tkuemmel said:
Thank you, but I have done all this. It appears like a lot of users have the same problem, no solution until now.
May be there is a little chance 4pda.ru, but I need a better translation.
Before the bootloop I dumped the original system, boot and recovery, but I'm not able to make a flashable zip of it. May be this would still be a better chance to bring the tablet back to life...
Click to expand...
Click to collapse
The Firefox browser has addons that will translate the whole web page.
I have an Asus tablet that I had recieved a replacement touchscreen for about 6 months ago but, i can't remember for the life of me where i had put all the screws. So everything for it is just in a protective case till i can find it. LOL!!!
Did your system come with windows?
My tablet had an android version of Windows in it and thought that yours may have had the same.
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**

Thanks for the tip, I'll try the addon. Hopefully its better than google translate (actually my russian should be pretty good as I learned it for 8 years in shool).
What is a android version of windows? I can't even thimk of something like that.
The tablet came with Lollipop and has a qualcomm chipset. I'd love to see some kind of bios and just flashing debian on it.
I'll try the russians again, may be I can manageto ask for a firmware package.
Good luck with the screws.
PS: Now I know, you mean something like windows rt?

Related

ROOT FAIL HELP PLEASE probably wrong spot but i'm new to android and i am panicking

i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.
UTubeMeBeach said:
i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2381582
http://goo.gl/lF0HEC
This is the driver you need to install to use ADB while in recovery which is different to the one for Fastboot and ADB while booted.
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
OMG if this works ill pm you and tell you
thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped
UTubeMeBeach said:
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped
Click to expand...
Click to collapse
If you insist, there should be a "Donate to Me" box next to my information on the left.
I had the same problem. Got stuck with no OS installed, USB debugging disabled, and no ROM I could flash. I was scared ****less but I ended up fixing it with a restore program.
Glad you got it fixed.
I learned how to unlock, root, flash custom kernels with my old nexus 7 before I attempted on my new nexus 7. Didn't want to make an expensive mistake. I looked at things here last year when I got my first n7, got confused and didn't attempt it. Now, I definitely won't go back to just stock. Hope you get it all sorted out! It was definitely scary for me the first time.
Sent from my Nexus 7 using Tapatalk 4
I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.
Geodude074 said:
I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.
Click to expand...
Click to collapse
It's mainly the word "brick" that gets on my nerves.
Most of these are really just bootloops or boot hangs. My last one was the latter (and a little unsettling, I'll admit). Turns out that trying to flash a root zip before you've signed into the tablet at least somewhere to create the sdcard directories just leads to a headache for me.

[Q] SM-T217s - my first ever brick.

Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
254336992952
​
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
IAMRUDYT said:
​
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.
sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.
Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app

[SOLVED] Please Help, PIT fails in ODIN and Heimdall

First off, let me start by saying that I was an idiot.
I've been flashing and rooting for years but this time I totally forgot about the change in bootloader from 4.3 to 4.4. So...
I was technically on 4.3 and decided to flash up to 4.4. I flashed everything (that included 4.4 bootloader) and got a PIT fail.
Now I cannot get it past the logo screen. I cannot download the PIT either.
Tried ODIN 3.7 and 3.9 (Using VMware) - always fails. I know I have the right drivers.
Tried Heimdall frontend and terminal. I always fail due to PIT check.
Flashing in recovery just tells me to install firmware via Kies but Kies doesn't recognize my device.
Phone still says that system status and current binary are custom so I believe I'm still rooted.
[SOLVED] Everything went smoothly on a regular PC. All these forum threads and yet I hadn't run into a single one that mentions you HAVE to use a PC rather than a virtual system or Heimdall in order to get this to work on a Galaxy Note 3.
I can tell you flashing on windows via vmware will fail every time. You must flash natively. Is this a Mac you are flashing on? If so, i'm afraid if you want Odin to work again you will have to boot camp your Mac.
Heimdall after the 4.4 bootloader will also fail every time. It only works for the initial flash (from 4.3 to 4.4), but after the 4.4 bootloader, it is a no go.
Sent from my SM-N900T using Tapatalk
noobtoob said:
I can tell you flashing on windows via vmware will fail every time. You must flash natively. Is this a Mac you are flashing on? If so, i'm afraid if you want Odin to work again you will have to boot camp your Mac.
Heimdall after the 4.4 bootloader will also fail every time. It only works for the initial flash (from 4.3 to 4.4), but after the 4.4 bootloader, it is a no go.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Thank you for your time. I am on a Mac and also figured that it probably had something to do with VMware. I'm glad to get a confirmation.
I am getting a replacement device today only because I need it for work so I couldn't afford to tinker with it this week.
p.s., I had tried several methods in other threads so I recognize your name. You are a gentleman and a scholar, good sir!
noobtoob said:
I can tell you flashing on windows via vmware will fail every time. You must flash natively. Is this a Mac you are flashing on? If so, i'm afraid if you want Odin to work again you will have to boot camp your Mac.
Heimdall after the 4.4 bootloader will also fail every time. It only works for the initial flash (from 4.3 to 4.4), but after the 4.4 bootloader, it is a no go.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Also, I'm was born and raised in Fresno. Moved out here in my early twenties. Small world!
conasabi said:
Also, I'm was born and raised in Fresno. Moved out here in my early twenties. Small world!
Click to expand...
Click to collapse
No kidding? I've been trying to leave Fresno forever, but the wife loves it here for some reason (family). Even when I was in the military, my wife lived here and made me live overseas and elsewhere in the country by myself. She only moved with me 3 times... Once to Oregon, once to the San Francisco area, and once down to Los Angeles. They were all very short tours also. Spent half my time overseas.
Sent from my 900T using Tapatalk

Lineage OS for LG v410 20170223

I upgraded Lineage OS 20170214 to 20170223 after the install the tablet boots through the splash screen the screen just turns black and hangs. I have waited up to 30 minutes and still just hangs on a black screen. Any ideas? I have to boot to recovery and install from backup.
Lineage 20170214 and earlier seemed to work except for the error listed bellow.
I imagine this is a carry over bug from CM 14.1 but I cant play any DRM videos from Google Play Movies. I can play trailers but anything purchased will not play. It does not matter if I download it or stream it. Usually it stops and just gives a "there was an error" prompt with out any specific error code. I say this was a carry over because I had the same problem in CM14.1.
Thank you for your time in reading this.
Kevinws42 said:
I upgraded Lineage OS 20170214 to 20170223 after the install the tablet boots through the splash screen the screen just turns black and hangs. I have waited up to 30 minutes and still just hangs on a black screen. Any ideas? I have to boot to recovery and install from backup.
Lineage 20170214 and earlier seemed to work except for the error listed bellow.
I imagine this is a carry over bug from CM 14.1 but I cant play any DRM videos from Google Play Movies. I can play trailers but anything purchased will not play. It does not matter if I download it or stream it. Usually it stops and just gives a "there was an error" prompt with out any specific error code. I say this was a carry over because I had the same problem in CM14.1.
Thank you for your time in reading this.
Click to expand...
Click to collapse
I believe that the following link can be very helpful regarding your issue:
[ANNOUNCEMENT] Important Lineage/LineageOS Information To Know... by Ibuprophen
I wish you the best of luck!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
Yes, I tried going from CM to Linage on this device using the 20170223 build. It was obviously bad and looks like it has been yanked off the downloads page as of today.
Unfortunately, I did not find Ibuprophen's answer to be terribly helpful. I looked at those references and it did explain to do an advanced wipe, but of course it never changed the outcome.
Just wanted you to know that I got the same results as you, and that you are not going crazy.
Thanks all who responded I really appreciate it.
Kevinws42 said:
I upgraded Lineage OS 20170214 to 20170223 after the install the tablet boots through the splash screen the screen just turns black and hangs. I have waited up to 30 minutes and still just hangs on a black screen. Any ideas? I have to boot to recovery and install from backup.
Lineage 20170214 and earlier seemed to work except for the error listed bellow.
I imagine this is a carry over bug from CM 14.1 but I cant play any DRM videos from Google Play Movies. I can play trailers but anything purchased will not play. It does not matter if I download it or stream it. Usually it stops and just gives a "there was an error" prompt with out any specific error code. I say this was a carry over because I had the same problem in CM14.1.
Thank you for your time in reading this.
Click to expand...
Click to collapse
The DRM issue has been resolved with the latest build. 14.1-20170317
A big thank you to all involved,
Kevinws42 said:
The DRM issue has been resolved with the latest build. 14.1-20170317
A big thank you to all involved,
Click to expand...
Click to collapse
I have installed lineage 14.1 with a tutorial every thing was ok but the wifi hotspot can't be activavted . that's why i want to install Marshmallow 6. To probe a tutorial that says works with android 6, in LG devices. Any tutorial you can sugest for the downgrade? Sorry for my bad english. Tank you in advance.

Unable to utilize SIM card and ROOT access

So I rooted and installed LineageOS 14.1 on my LG L70 (LG-MS323), I had rooted and installed CWM 6.0.5. I then used the latest nightly version of LineageOS 14.1 along with Micro GAPPS, to install the ROMs, I had wiped and formatted everything, from the cache to the system, then did an install.
Once I flashed the ROM, and went through setting up everything, it seems to run fine, but I have two issues as of right now: my SIM card is not being recognized, when I go to the Cellular Networks page to manually set this all up, it then displays an error that "com.android.phone has stopped working". No idea why I am receiving this error message.
Second - for some reason, I have enabled root to be accessible for both apps and ADB, but apps are unable to verify the root. The normal popup when allowing root access to an app is not appearing, so I have no idea why this isn't working either.
This is my first time rooting this device, and I am suspecting that maybe because I used CWM and not TWRP that is the reason my issues above (and others I may not be aware of yet) are appearing? Can anyone help me figure out what I should do? Or is there another ROM out there that I should consider? I was using this device as a daily, so being able to use the phone with all functionality is very appreciated.
darkgiant said:
So I rooted and installed LineageOS 14.1 on my LG L70 (LG-MS323), I had rooted and installed CWM 6.0.5. I then used the latest nightly version of LineageOS 14.1 along with Micro GAPPS, to install the ROMs, I had wiped and formatted everything, from the cache to the system, then did an install.
Once I flashed the ROM, and went through setting up everything, it seems to run fine, but I have two issues as of right now: my SIM card is not being recognized, when I go to the Cellular Networks page to manually set this all up, it then displays an error that "com.android.phone has stopped working". No idea why I am receiving this error message.
Second - for some reason, I have enabled root to be accessible for both apps and ADB, but apps are unable to verify the root. The normal popup when allowing root access to an app is not appearing, so I have no idea why this isn't working either.
This is my first time rooting this device, and I am suspecting that maybe because I used CWM and not TWRP that is the reason my issues above (and others I may not be aware of yet) are appearing? Can anyone help me figure out what I should do? Or is there another ROM out there that I should consider? I was using this device as a daily, so being able to use the phone with all functionality is very appreciated.
Click to expand...
Click to collapse
Have you seen the following thread?
http://forum.xda-developers.com/showthread.php?t=2698621
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
Ibuprophen said:
Have you seen the following thread?
http://forum.xda-developers.com/showthread.php?t=2698621
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
Click to expand...
Click to collapse
Yeah I tried that, but the problem is, when I go to cellular networks so I can enter a custom APN, it just gives me an error, which is essentially not allowing me to really access any of that portion within the ROM.
I also am having issues with ROOT access with the ROM, so no idea why that's not working properly

Categories

Resources