Related
Hi all, hope you can help me. I've tried searching on the internet but no-one seems to be having any problems like mine. and my phone is now near enough bricked.
So i bought a LG G2 D802 from aliexpress, all working fine but no 4g lte option for some reason. Had a look around and seems updating to stock europe rom would have sorted this so i thought id do this.
So Updated the rom using flashtool2014, downloaded lg usb drivers, the europe rom D80220D_00 and lgmobile support tool. Went through the process and it all ran fine with no errors completed 100%and then said done pressed exit and disconnected phone.
Now, switched phone on . Straight away touch completely messed up click on the screen and different parts keep of the screen keep clicking. Eventually after 15mins managed to get out of the startup where it asks for wifi settings etc so i could try to factory reset. No luck even out of startup have not yet managed to get to the screen for usb debugging yet due to random screen clicking (keeps opening other apps, screens).
I cannot rerun the flashtool as i cannot enable usb debugging or even switch away from charge only to pc softwarw and it just says phone not connected on the flashtool and keeps ending.
Switched off by holding power button for long time. Holding down the down button and power does nothing just keeps restarting when i eventually let go.
Also sim is in phone but it says service disabled?
Any ideas how i can fix the phone! All was working fine before I did the europe rom update
Thanks
Jon
You can connect a mouse via otg and navigate to usb debug
Sent from my SM-N910H using XDA Free mobile app
Maybe try factory reset and just use mobile support tool update stock rom?
Sent from my LG-D803 using XDA Free mobile app
I would just use a wireless keyboard with an otg cable like sugested before
Sent from my LG-D805 using XDA Free mobile app
I eventually managed to select lg software as connection mode and flashed to another firmware but exact same issue again.
After trying for ages and opening the wrong thing again and again i managed to get to the screen in settings to click 5 times to enable developer options however now the screen just freezes and then you get a message saying settings has stopped working and phone locks up. This has happened 3 times since. Doesnt seem like anyway to get it sorted if i cant enable usb debugging.
Also it seems to be that the firmware change has erased the imei and that is what is causing all these problems. I found one site that details how to restore but once again you need usb debugging enabled.
Droidview has the page where you have to backup and restore imei, i dont have a backup so will need method 2. If i can get usb debugging enabled that is!
JON-JAY said:
I eventually managed to select lg software as connection mode and flashed to another firmware but exact same issue again.
After trying for ages and opening the wrong thing again and again i managed to get to the screen in settings to click 5 times to enable developer options however now the screen just freezes and then you get a message saying settings has stopped working and phone locks up. This has happened 3 times since. Doesnt seem like anyway to get it sorted if i cant enable usb debugging.
Also it seems to be that the firmware change has erased the imei and that is what is causing all these problems. I found one site that details how to restore but once again you need usb debugging enabled.
Click to expand...
Click to collapse
Try using onscreen phone maybe you could manage to set that up and then enable usb debugging?
.::.LG G2 D803.::.
.::.CLOUDYFLEX 2.7.::.
thanks for all the help, lg on screen just didn't work for some reason wouldn't connect to the phone. Was thinking about a otg cable but after an hour of clicking again and again I managed to get the developer options and usb debugging enabled.
I went through the procedure at droidview to restore imei using qpst but after finding the com port it says no phone detected so theres nothing more I can do, looks like I just have to accept this brand new brick lol.
Anybody know anywhere in London that does repairs like this, I have tried a couple of shops in London Victoria near work but they couldn't do anything. Apparently theres something called an octoplus/octopus box that can fix LG G2 imei or flash firmware.
Thanks again for everyones suggestions. .
Jon-jay, I have the same issue. I tried the "easy" kdz flash and tot flash and basically bricked my phone. The phone turns on but the screen is calibrated incorrectly like you describe so I can't click anything without trying over and over. I click one area of the screen and another is activated. I can pull down the notification pane but can't click anything in there. The phone is in a boot loop too if I don't touch it. I also want to turn on USB debugging so I could try to restore with adb or fastboot. I will let you know if I find anything.
Yeah very tricky to fix this phone after flashing. Ive flashed loads of lg phones with the flash tool and never any problems until now. Ive currently sent to a shop in south wimbledon who quoted me £50-£80 for repair if he could fix it. I dropped it off on mon and still no response so im not holding my breath. It seems this phone will be going to the recyclers if he cant do anything.:crying:
JON-JAY said:
thanks for all the help, lg on screen just didn't work for some reason wouldn't connect to the phone. Was thinking about a otg cable but after an hour of clicking again and again I managed to get the developer options and usb debugging enabled.
I went through the procedure at droidview to restore imei using qpst but after finding the com port it says no phone detected so theres nothing more I can do, looks like I just have to accept this brand new brick lol.
Anybody know anywhere in London that does repairs like this, I have tried a couple of shops in London Victoria near work but they couldn't do anything. Apparently theres something called an octoplus/octopus box that can fix LG G2 imei or flash firmware.
Thanks again for everyones suggestions. .
Click to expand...
Click to collapse
Check out the thread lg g2 is unbrickable now, it involves shorting a couple capacitors to unbrick but its ingeneious. I bet itll help you out.
.::.LG G2 D803.::.
.::.CLOUDYFLEX 2.7.::.
the plot gets thicker...
okay so it has been a few months now and I revisited the phone sitting around. This is how I got on:
I gave the phone to shops in London, no-one could fix it got it back first week of Jan. So I thought I'd retry myself.
One guy told me that the imei may be for D802 but the screen and insides of the phone is a d800 model.
That makes sense as the touch works erratically. This was a refurbished phone I bought from aliexpress which claimed to be a EUR D802 but after I took the back cover off it says D800\d801\d803 inside on a lot of the flex connections and at the bottom of the plastic it says d800. I downloaded the AT&T stock rom and flashed with octoplus - touch worked perfectly! but phone kept restarting itself and looping really badly so I put in download mode and went back to D802 uk firmware - and touch not working again.
(Prior to this I bought the octopus box also in the hopes that restoring the imei I had previously lost will somehow be related to the screen.
This worked in restoring imei only and I have restored the d802 imei with octopus box)
Anyhow I then flashed stock uk firmware on the phone so everything in the phone works perfectly fine except the touch! so I am controlling touch with otg cable and mouse.
my next thought was install a d800 custom rom it will fix the touch! Now I then rooted, and installed d802 autorec.apk. I came on xda and downloaded a d800 stock custom rom (D80020k) from the AT&T subsection and thought I'd install this through twrp. All though the custom rom says successful when I reboot it comes to fastboot mode again. so I then go about restoring the stock d802 firmware. I installed d800 autorec.apk but that too send to fastboot mode.
So I am lost. Everything working perfect except the touch. Any ideas anyone? Im hoping some one says there is a stock lg custom rom that has all the screen settings for d800/01/02/03 which will sort my problem!
What it seems is the chinese company selling the refurb has somehow managed to get a d802 imei on a d800/01/03 not entirely sure how this is possible either!
JON-JAY said:
What it seems is the chinese company selling the refurb has somehow managed to get a d802 imei on a d800/01/03 not entirely sure how this is possible either!
Click to expand...
Click to collapse
What they're doing is flashing a d802 system.img with otherwise d800/01/03 firmware.
I saw a thread in the T-Mobile G2 area saying to get d802 on your d800/d801 you just flash a custom d802 rom and then a d800/801 kernel but this causes my phone to go back to fastboot...still lost! the custom rom works fine itself (Except for touch again!)
JON-JAY said:
I saw a thread in the T-Mobile G2 area saying to get d802 on your d800/d801 you just flash a custom d802 rom and then a d800/801 kernel but this causes my phone to go back to fastboot...still lost! the custom rom works fine itself (Except for touch again!)
Click to expand...
Click to collapse
There is a way to get them back to their original frankenphone state but it's quite a procedure. Flash d802 firmware. Use a otg usb mouse to navigate since it'll have touch issues. Root and install custom recovery using the actual hardware as your guide to which twrp version to install. D800 in your case. Do a nandroid backup. Move the nand backup to your pc for safe keeping. Now install d800 firmware using a hex edited tot to allow it to proceed and a generic dll to avoid cross dll issue. Root, install twrp again. Move twrp backup from pc to phone. Do a restore but only restore the system.img. Now you have firmware that cooperates with d800 hardware while appearing and acting like a d802 in every other way.
The other thought I had but have not tested yet would be to flash d800 firmware right off the bat, then root and install twrp. Then use dd to flash system.img to it's partition ( /dev/block/mmcblk0p34 ). I'm not sure how that would work due to the very large size of the system image. You'd have to extract it from the kdz. Because it's so large when it's extracted, it does it in parts so it must be merged back together to make one file. But if it did work, it'd save the step of having to root/recovery twice on two separate firmwares.
a few feeks ago bought a second hand lg g2 d802 running kitkat 4.4.2 wich was only detecting 2g when i try to connect to the internet, i tried to solve this problem by entering the hidden menu and selecting the network types it could detect but no luck, so i decided to upgrade to lollipop, i downloaded the lg support tool and went for it, when the update was done i found myself with an almost completly functioning device except it had the "imei=null" problem, meaning no network at all --"
i tried the QPST but it was unable to detect my phone, so i decided to root my phone and go for a custom rom, the cyanogenmod13 nightly (i don't really know what i was thinking at that point :s ) and when done i was stuck in a bootloop, so i tried flashing a stock rom kdz method but the lg flash tool would stop automatically. since then i've been trying to flash stock TOT roms, the process would stop at 94% and the phone reboots. the screen shows random pixels and lines, the start up lg tune is there and i feel vibration when i press the home buttons location, i've tried to reset it to factory settings and i've used theLGUP_8974.dll, selecting the BOARD DL option in the lg flash tool but that didn't solve the problem. i have read somwhere that it could be a kernal problem, i don't know if i should go that way ( am at that point where i don't want to mess up my device anymore xD ) what do you guys think?
thank you for your help
restlessone said:
a few feeks ago bought a second hand lg g2 d802 running kitkat 4.4.2 wich was only detecting 2g when i try to connect to the internet, i tried to solve this problem by entering the hidden menu and selecting the network types it could detect but no luck, so i decided to upgrade to lollipop, i downloaded the lg support tool and went for it, when the update was done i found myself with an almost completly functioning device except it had the "imei=null" problem, meaning no network at all --"
i tried the QPST but it was unable to detect my phone, so i decided to root my phone and go for a custom rom, the cyanogenmod13 nightly (i don't really know what i was thinking at that point :s ) and when done i was stuck in a bootloop, so i tried flashing a stock rom kdz method but the lg flash tool would stop automatically. since then i've been trying to flash stock TOT roms, the process would stop at 94% and the phone reboots. the screen shows random pixels and lines, the start up lg tune is there and i feel vibration when i press the home buttons location, i've tried to reset it to factory settings and i've used theLGUP_8974.dll, selecting the BOARD DL option in the lg flash tool but that didn't solve the problem. i have read somwhere that it could be a kernal problem, i don't know if i should go that way ( am at that point where i don't want to mess up my device anymore xD ) what do you guys think?
thank you for your help
Click to expand...
Click to collapse
Sounds like to me you may not have a D802. You'll need to take the back cover off, and look and see what model #s you see. As if your having screen issues that sounds like your flashing a D802 firmware on a D800 or D801.
Also remember flashing will almost always stop before 99%.. Anything after 85% its done this is normal and will almost always happen.
These D802's have a LONG history (mostly bought referbs) of not being what they are being sold as.
hyelton said:
Sounds like to me you may not have a D802. You'll need to take the back cover off, and look and see what model #s you see. As if your having screen issues that sounds like your flashing a D802 firmware on a D800 or D801.
Also remember flashing will almost always stop before 99%.. Anything after 85% its done this is normal and will almost always happen.
These D802's have a LONG history (mostly bought referbs) of not being what they are being sold as.
Click to expand...
Click to collapse
the problem has been solved, it tuned out to be an ls980, now my G2 is fully back to life :laugh: thanx alot hyelton for your help :good:
Hello everyone,
I have a friend who uses a S4. He was on marshmallow 6.0.1 twrp3.0.2.0. Suddenly the phone turns off, and wont boot anymore to android.
We tried to wipe data+cache+system+dalvik, and install MM 6.0.1 again and install stock 4.4.4 and 5.0.1. All led to fail.
Is it a pit file case or a broken bootloader ? Or it might be some sort of hardware issue ? Thank you.
Could be hardware.
What is the Odin error message when trying to flash stock roms?
It might be a hardware.
No error occurs in odin. It flashes and passes !!
But when i try to boot, the phone always gets stuck on SAMSUNG.
Yeah, you're not doing anything wrong, probably a hardware issue
Samofr said:
But when i try to boot, the phone always gets stuck on SAMSUNG.
Click to expand...
Click to collapse
It's probably the GPU.
Recovery and download mode don't need the GPU to function, so that's why they work.
But android does need it, so that why it doesn't work.
I took the phone to a mobile shop today.. The guy told me that overheating caused this.
Very bad news
But this is so weird.. We all know that the s3 at previous versions of android OS used to boil on moderate~heavy usage and i'm still on my s3 since 2012, and it still didnt show any kind of hardware-related problems... But anw i think i should stick to a safe side and start backing up my important stuff online
Samofr said:
I took the phone to a mobile shop today.. The guy told me that overheating caused this.
Very bad news
Click to expand...
Click to collapse
Sorry about your phone mate..
Hello everyone.
My device is going into bootloop without usb cable.
With USB power adapter device works fine but when I pull out the cable smartphone is going to reboot (logo->reboot->logo->reboot...).
I tried the next:
I have changed battery to new but result is the same.
I have updated firmware through official Samsung SmartSwitch program but it also didn't help.
Recovery and bootloader are reachable.
I found info on stackoverflow that some crash logs could be stored by path /data/anr.
But my device isn't rooted and I can't get files from specified path.
Baseband ver. - N910HXXU1DPC1
Build number - MMB29K.N910HXXS2DQC7
Device status - official
Could someone suggest me some steps to check ?
Thanks in advance !
Re Flash to stock firm
To solve your problem you may have to download Stock firmware from sam mobile.com. Re-flash device using Odin3. Ive been dealing with a similar issue, and have had to do this several 100 times over the course of 3 day. It should solve your boot loop problem, but whatever else to are trying to do i'm not sure.
milesg86 said:
To solve your problem you may have to download Stock firmware from sam mobile.com. Re-flash device using Odin3. Ive been dealing with a similar issue, and have had to do this several 100 times over the course of 3 day. It should solve your boot loop problem, but whatever else to are trying to do i'm not sure.
Click to expand...
Click to collapse
Hello milesg86.
First of all thanks for your advice. But I think it will not help me.
I'll try to explain why.
I have already checked the latest firmware version for my device for my country on sammobile.com - it's N910HXXS2DQC7.
It's the same version that I reinstalled using SmartSwitch http://www.samsung.com/us/smart-switch/ .
Could it be the bug in firmware ?
Should I check some logs ?
you tried factory reset over recovery already? anyways: there are so many possible reason for a bootloop at Note4 --> mmc fail etc
Galixy said:
you tried factory reset over recovery already? anyways: there are so many possible reason for a bootloop at Note4 --> mmc fail etc
Click to expand...
Click to collapse
Yes, I have done factory reset through official recovery.
Also, I reinstalled firmware through SmartSwitch.
But both variants didn't help (
Galixy said:
you tried factory reset over recovery already? anyways: there are so many possible reason for a bootloop at Note4 --> mmc fail etc
Click to expand...
Click to collapse
Could you suggest how to check mmc fail ?
Fediir said:
Yes, I have done factory reset through official recovery.
Also, I reinstalled firmware through SmartSwitch.
But both variants didn't help (
Click to expand...
Click to collapse
Did you install a specific app or update before the loop occured? However it smells like a defect mainboard. Here is the deal: You can try root your phone (if the factory reset worked there should be a OS on your Note 4) and flash custom recovery like TWPR. Then do a FULL wipe through it and flash the OS you downloaded again through ODIN mode. Dunno how experienced you are with it but keep in mind you do it on your own risk and the warranty is gone (if you still got it anyways.....)
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
well, if the mmc fail would occur you would definitely recognize it
Galixy said:
Did you install a specific app or update before the loop occured? However it smells like a defect mainboard. Here is the deal: You can try root your phone (if the factory reset worked there should be a OS on your Note 4) and flash custom recovery like TWPR. Then do a FULL wipe through it and flash the OS you downloaded again through ODIN mode. Dunno how experienced you are with it but keep in mind you do it on your own risk and the warranty is gone (if you still got it anyways.....)
---------- Post added at 09:11 PM ---------- Previous post was at 09:08 PM ----------
well, if the mmc fail would occur you would definitely recognize it
Click to expand...
Click to collapse
I have installed TWRP through Odin 3.12 recently (without root) https://twrp.me/devices/samsunggalaxynote4exynos3g.html.
Why you suggest to root the device ?
I want to clarify. Do you recommend to flash the official OS through Odin ?
What is the benefits from TWRP wipe ?
Also, now I am going to install this firmware https://forum.xda-developers.com/note-4/development/rom-nemesis-refined-v3-5-n7port-t3587637 .
Do you recommend it ?
P.S. Phone is working when connected to USB power adapter.
Thank you for comments !
Fediir said:
I have installed TWRP through Odin 3.12 recently (without root) https://twrp.me/devices/samsunggalaxynote4exynos3g.html.
Why you suggest to root the device ?
I want to clarify. Do you recommend to flash the official OS through Odin ?
What is the benefits from TWRP wipe ?
Also, now I am going to install this firmware https://forum.xda-developers.com/note-4/development/rom-nemesis-refined-v3-5-n7port-t3587637 .
Do you recommend it ?
P.S. Phone is working when connected to USB power adapter.
Thank you for comments !
Click to expand...
Click to collapse
Has been a while that i used TWPR but i guess, when you trying to do a full a wipe it's telling you anyways if the device is not rooted?
TWPR does a FULL wipe, which means your smartphone is "empty". It wont boot then because there is no OS anymore, so you flash through odin (hold volume down, home button, powerbutton) your stock firmware. On Note 4 i never had an custom rom, only on the old Note 2 and CM rom was pretty nice. I think they stopped working on CM but i am sure you will find a stable version for your phone right here in the forum
NEMESIS ROM was successfully installed but it didn't solve the problem
Device is going to reboot/bootloop when I remove the USB power cable.
The next step is the authorized Samsung service.
Thanks to all for comments.
P.S. NEMESIS ROM :good::good::good: I'll install it again when my phone will be fixed .
Hello to everyone.
Yesterday my problem was solved.
Issue was because of damaged battery. Authorized Samsung service provides to me original battery and it's work
As result, I requested fefund for my Amazon order of battery https://www.amazon.com/gp/product/B00SW22RJU/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 .
Thanks to all for comments !
I know this is an old thread but ive been going through this issue for a long time. But now recently happened to my galaxy s7 edge, exact same problem.
It only stays on with the charger cable connected, if i remove it, it goes to bootloop.
On the note 4 ive tried 4 different batteries, they all say samsung but not sure if they're oem from samsung. But i also swapped the mother board and also same thing happens , so its not the mother board thats damaged cause I tried 2 of them and same issue. Could be it be the charging port or should try a oem battery too ?
fevera1985 said:
I know this is an old thread but ive been going through this issue for a long time. But now recently happened to my galaxy s7 edge, exact same problem.
It only stays on with the charger cable connected, if i remove it, it goes to bootloop.
On the note 4 ive tried 4 different batteries, they all say samsung but not sure if they're oem from samsung. But i also swapped the mother board and also same thing happens , so its not the mother board thats damaged cause I tried 2 of them and same issue. Could be it be the charging port or should try a oem battery too ?
Click to expand...
Click to collapse
Then you have 2 bad mother boards...... anything that would cause the bootloop is in the motherboard
trinilu27 said:
Then you have 2 bad mother boards...... anything that would cause the bootloop is in the motherboard
Click to expand...
Click to collapse
Well its basically the same info that the person that did this thread. Same exact thing. I just havent tried a new oem battery i guess just knock off ones. But now also with this s7 edge is also happening
fevera1985 said:
Well its basically the same info that the person that did this thread. Same exact thing. I just havent tried a new oem battery i guess just knock off ones. But now also with this s7 edge is also happening
Click to expand...
Click to collapse
I did have
..i Have had a bad battery with one of my Note 4 S the phone would be fine until the battery got below 50% then it would constantly reboot.... Now is your phone looping or is it just stuck on the splash screen?
trinilu27 said:
I did have
..i Have had a bad battery with one of my Note 4 S the phone would be fine until the battery got below 50% then it would constantly reboot.... Now is your phone looping or is it just stuck on the splash screen?
Click to expand...
Click to collapse
Well for example if I have the phone connected to the charger, it will stay on like normal, I can make calls, use the internet etc.. Normal stuff. If I unplug the cord and say the battery is 100% it will sometimes stay on for like 5 mns and then it shuts off and starts restarting on and on to samsung screen or sometimes the carrier logo screen. It will do that for like 2 mns then it shuts off and wont turn on.
I plug it on the charger and battery shows 0% or 3 sometimes, but 5 mns before it was 100%..
Hopefully i make sense lol
fevera1985 said:
Well for example if I have the phone connected to the charger, it will stay on like normal, I can make calls, use the internet etc.. Normal stuff. If I unplug the cord and say the battery is 100% it will sometimes stay on for like 5 mns and then it shuts off and starts restarting on and on to samsung screen or sometimes the carrier logo screen. It will do that for like 2 mns then it shuts off and wont turn on.
I plug it on the charger and battery shows 0% or 3 sometimes, but 5 mns before it was 100%..
Hopefully i make sense lol
Click to expand...
Click to collapse
I take back what I said....I'll bet it is the battery....trust me if you're going to go buy a new battery pay out the little extra money for the extended battery you can find them on eBay and Amazon...well worth it
trinilu27 said:
I take back what I said....I'll bet it is the battery....trust me if you're going to go buy a new battery pay out the little extra money for the extended battery you can find them on eBay and Amazon...well worth it
Click to expand...
Click to collapse
Right.. I bought some local in a local phone store but those are fake. They have the samsung brand but its one of those places they repair phones and I knoe they're fake batteries. But yeah they didnt work. I found a authentic oem batteries on ebay that I'm going to order and crossing my fingers it works.
I have a Samsung Note 4 with boot loop problem. I am asking for advice because it has two Bitcoin Accounts on it that I can not retrieve anywhere else. HELP!!! Thanks in advance
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Wellfare11 said:
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Click to expand...
Click to collapse
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
weazie said:
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
Click to expand...
Click to collapse
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Wellfare11 said:
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Click to expand...
Click to collapse
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
weazie said:
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
Click to expand...
Click to collapse
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Wellfare11 said:
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Click to expand...
Click to collapse
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I already tried, I installed the rom corresponding to the model of the cell phone and the wifi still does not work, the base band is still unknown, I also checked if the sim card was correctly placed, and everything is fine
weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Wellfare11 said:
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Click to expand...
Click to collapse
Great that you have an idea. ?
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea. ?
weazie said:
Great that you have an idea.
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea.
Click to expand...
Click to collapse
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Wellfare11 said:
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Click to expand...
Click to collapse
Does the phone ask for a pin code at any point?
weazie said:
Does the phone ask for a pin code at any point?
Click to expand...
Click to collapse
does not request any code at any time
Wellfare11 said:
does not request any code at any time
Click to expand...
Click to collapse
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. ?*
weazie said:
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. *
Click to expand...
Click to collapse
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Wellfare11 said:
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Click to expand...
Click to collapse
Hello, colud you solve the problem? Because I am havig a very similar one...
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
I have the exact same problem, I wasn't able to repair it so I sent it to service and tomorrow they will try to fix it for $35. The problem with goign back to previous versions is that you loose the IMEI and MAC . The problem with the pie version I believe is the baseband. If the service is able to fix it I will post the solution here for you to fix it .
bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
caradobeco said:
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
Click to expand...
Click to collapse
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
juampapo546 said:
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
Click to expand...
Click to collapse
I am still working on this, I actually did this to a work phone (I had permission to root/unroot). Something that has helped me so far is just getting familiar with the whole flashing process - https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/. I think from this article the problem lies in the modem/radio rom. That *should* be the only thing you need to flash on. However, I have noticed with a lot of roms on here, a modem rom is not included on the stock firmware. But that needs to match well to your phone from what I understand. I have tried a few modem roms already, unfortunately, but no luck.