after rooting the phone,when i started the phone,it kept restarting after 2 min.
then i installed the radio.img.
after flashing radio.img the imei and the baseband number is not showing
Sim is also not running
it shows that "no 4g simcard ,oleasr insert sim card"
please help
Which root method did you use and why did you flash the radio image and how? Also do you have twrp recovery?
Sent from my SM-G920P using Tapatalk
i first unlocked the bootloader from htcdev and then flashed supersu
after that when i restarted the phone ,imei was removed.
yes i have twrp installed
Related
I think I solved my no Baseband Problem. I could see IMEI in Fastboot but not in OS. With Sense roms it boot looped no radio. With OneDroid I could access the OS no bootloop but no baseband no IMEI. Im with Bell Canada. Someone posted an RUU for bell 129. Ran that, no success still bootloop. I flashed GE 4.4.2 firmware, erase cache, reboot. Then Flashed flashed Philz M7UL recovery, then flash OneDroid. I did all of this with NO SIM installed. Then let it boot configured the options. Chose skip Cyan, Chose Skip Google Acct then Airplane mode then inserted Sim, then took off Airplane mode. Hope this helps!
Hello Everyone as stated.
I have an international variant of HTC One HTL22. I am also using a mac OS computer.
I unlocked the bootloader and had s off and CID as 111111
The phone was also rooted.
So first I paid a guy in japan to s off and cid the phone along as rooting the phone.
THen I unlocked bootloader.
I downloaded the Android Revolution HD's latest rom.
I flashed into recovery and it went into Clockworkmod.
I wiped and erased all the cache. I installed the ROM and everything seemed going fine until i rebooted the phone.
Now its stuck on the bootloop and always trying to go into recovery but failing. I can get into a different menu by pressing power and volume down. But everytime i try and click factory reset or anything else it just boots into a loop again.
I tried accessing the phone on the Mac OS Terminal but it is not showing up when i try and type up adb devices on the terminal (command prompt)
Please help! I am desperate here!!
ShadowKage said:
Hello Everyone as stated.
I have an international variant of HTC One HTL22. I am also using a mac OS computer.
Click to expand...
Click to collapse
Afaik, the HTC One HTL22 (M7_WLJ) is not an international variant, its a Japanese variant for KDDI carrier
I downloaded the Android Revolution HD's latest rom.
I flashed into recovery and it went into Clockworkmod.
Click to expand...
Click to collapse
From arhd thread:
For HTC One International GSM/LTE (UL), International GSM (U), all U.S. carriers (apart from Sprint) (click here for more details)
Click to expand...
Click to collapse
Yours is a M7_WLJ, not a M7_UL neither a M7_U. Unless you have download a version of arhd modified to run on your WLJ, you have flashed a rom not compatible with your phone...
Now better to head to this thread:
http://forum.xda-developers.com/showthread.php?t=2680107
I tried accessing the phone on the Mac OS Terminal but it is not showing up when i try and type up adb devices on the terminal (command prompt)
Click to expand...
Click to collapse
ADB only works from a booted rom or from custom recovery, in bootloader you must use fastboot commands, i.e fastboot devices
alray said:
Afaik, the HTC One HTL22 (M7_WLJ) is not an international variant, its a Japanese variant for KDDI carrier
From arhd thread:
Yours is a M7_WLJ, not a M7_UL neither a M7_U. Unless you have download a version of arhd modified to run on your WLJ, you have flashed a rom not compatible with your phone...
Now better to head to this thread:
http://forum.xda-developers.com/showthread.php?t=2680107
ADB only works from a booted rom or from custom recovery, in bootloader you must use fastboot commands, i.e fastboot devices
Click to expand...
Click to collapse
I see I flashed an incompatible rom.
So now I am stuck in a boot loop. It seems I am able to go onto fastboot and the Terminal (CMD) recognizes the device but I cant get the ADB to recognize the phone.
I don't know what to do after that. Can I flash a compatible rom using an SD card? Or does it have to be on the internal storage?
How do I get it back so that it just loads back onto the stock ROM that it once had?
edit: yeah so I went into fastboot and erased cache which got me back into clockwork mod and using an SD card I tried installing the HTC J One Maximus Rom and the HTCsoku Global Edition ROM and everytime it reboots it just keeps getting stuck on the htc logo entering or trying to enter recovery mode.
Bootloader is still unlocked, S-OFF, CID11111. When I got the phone back from the service guy.
All I did was unlocked the bootloader. He rooted the phone already. So I was hoping to just install a working ROM and then unlock the SIM on the phone.
Any help/advice/ is always appreciated for sure.
ShadowKage said:
I see I flashed an incompatible rom.
So now I am stuck in a boot loop. It seems I am able to go onto fastboot and the Terminal (CMD) recognizes the device but I cant get the ADB to recognize the phone.
Click to expand...
Click to collapse
Maybe it was not clear:
ADB only works from a booted rom or from custom recovery If you can't make ADB works from custom recovery, your drivers are probably not installed correctly.
I don't know what to do after that. Can I flash a compatible rom using an SD card? Or does it have to be on the internal storage?
How do I get it back so that it just loads back onto the stock ROM that it once had?
Click to expand...
Click to collapse
You might want to check this thread. here you can find custom recovery and custom rom for your HTL22. Look at the last page, there is an updated rom list for your phone variant.
You can probably flash the rom both from the sdcard or from the internal storage. You can push the rom to your internal storage using ''adb push'' command from twrp recovery.
alray said:
Maybe it was not clear:
ADB only works from a booted rom or from custom recovery If you can't make ADB works from custom recovery, your drivers are probably not installed correctly.
You might want to check this thread. here you can find custom recovery and custom rom for your HTL22. Look at the last page, there is an updated rom list for your phone variant.
You can probably flash the rom both from the sdcard or from the internal storage. You can push the rom to your internal storage using ''adb push'' command from twrp recovery.
Click to expand...
Click to collapse
well after a painful 12 hours I managed to flash a twr recovery that worked. I was able to flash a 4.4 kitkat rom with sense 6.0.
I have an au kddi Iphone 4s micro sim and I want to input that onto the HTC one. I dont think I need to unlock sim for it as its on the same network.
However, when I try to put it on the phone.....I get no signal. I tried WDCMA only and GSM only and to no avail. Any advice?
Thread closed,
Thread has been closed at OP's request
Many thanks,
Ghost
Hey
If u have flashed FTF or any other zip and lost your IMEI/Service And Major Issue Loosing Root status and unable to flash kernel/recovery using fastboot or flashtool
Rooting Status Unknown in service menu Configuraton *#*#service#*#*
Then you can revert back in two cases.
Case 1
That Worked for me.
You Have TWRP OR CWM Backup of previously working Firmware.
Steps:
1. Install Flashtool & Drivers. If you have already installed,Remove and reinstall. use 0.9.18.4 that worked for me.
2. Follow these steps.
A. Open C:/Flashtool/Custom/mydevices/
B. View The video for further steps and close flashtool folder.
https://www.youtube.com/watch?v=Qkl9UyrQKSo
after above steps/Check wether you can flash Kernel/Recovery Using flashtool/If u succeeded then Cheers.
Otherwise procede to next step.
C. Relock ur bootloader using flashtool. U may have to try 2 to 3 times if it failed/Check adb fastboot drivers,I tried 5 to 6 times and then it relocked my bootloader. If it is locked, dont unlock yet.
3. Download and flash Kitkat 4.4.4 Firmware using flashtool.
4. Download XZDR From the link
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 [email protected][NUT]'s for awesome work.
5. Start it and browse for Superuser.zip(Copy to storage),Install Kingroot v 4.5 and Busybox and install to phone.
6. Check root status if successfully rooted then Open XZDR and extract it. Run .bat file and check your phone,Give root permission. your phone will reboot to recovery.
7. Now
Wipe cacche/Dalvik/System/Data
8. Install twrp backup that you have already stored in cell phone.
9. Install Superuser.zip. Again Wipe cache/Dalvik cache only.
10. Reboot your phone and all set.
Method 2
If yo dont have twrp backup.
Relock bootloader/Flash Kitkat and root it using above steps.
One you installed recovery. Reboot to recovery and do steps 7 to 10.
Cheers
I have a similar problem, Please Help me
I was flashing a stock rom for my xperia z3 D6653. On flashtool I unticked "SIMLOCK" in MiscTA Exclude. (<----i think This was the problem)
After that, the flashing proccess started and done without any problem. When i put the sim card in the phone, it says: "Invalid Sim card" and in the service menu says: "Rooting status: Unknown". Before this, the service menu said: "Rooting status: Unlock Bootloader allowed: yes" then I unlocked my bootloader without any problem and everything was perfect, but after that flashing on flashtool the Rooting status change to "Unknown" and my sim card are unable to read. There is no problem with my sim card because I tried to put it on another phone and works perfect.
How do I fix it?
How I change the roothing status back to "allowed: yes"
and how I fix it to be able to read my sim card again?
sorry for my horrible english.
Please help me to solve it, im a noob in this kind of things and i dont know how to follow the tutorial.
Well this definitely has something to do with the TA partition. I also installed the 228 update yesterday which resulted in a non-working SIM, together with the "Rooting status: Unknown" error.
After creating a TWRP backup, I just flashed KK 4.4.4 (.292) onto my device. This however did not solve my problem, as it still showed "Rooting status: Unknown".
I have just restored my saved TA-partition (I made a dump of it before unlocking the bootloader months ago, http://forum.xda-developers.com/showthread.php?t=2292598) and this has fixed my problem!!! It now shows "Rooting status: Unlock Bootloader allowed: yes".
So, if you have saved your TA-partition you can try to restore it onto your device. Otherwise you could try to relock and unlock your bootloader, hopefully this will solve your problem.
Good luck
now my phone lags freezes crashes reboots and does random weird s*** all the time I figured out that the files that came out on the SD card when I ran the script are from /firmware-modem/image. My phone is a mess HELLLLL LP
A folder named image came out on the SD card when I ran the unlock_N4 file. When I reflash stock Odin firmware it gave me an error message device does not have drk please indlstall drk and press any button and DMVerity verification failed when it went into recovery afterwards. The serial number is off also. Anybody know how to use fastboot with ADB to flash all the files back in????
did you try Kies?
lincolnsxda said:
now my phone lags freezes crashes reboots and does random weird s*** all the time I figured out that the files that came out on the SD card when I ran the script are from /firmware-modem/image. My phone is a mess HELLLLL LP
A folder named image came out on the SD card when I ran the unlock_N4 file. When I reflash stock Odin firmware it gave me an error message device does not have drk please indlstall drk and press any button and DMVerity verification failed when it went into recovery afterwards. The serial number is off also. Anybody know how to use fastboot with ADB to flash all the files back in????
1st why you ran Verizon bootloader to this phone? this phone has unlocked bootloader it doesnt need to be unlocked
2nd your phone partition got messed up you have to put TWRP back and then go in wipe and then you have to do file repair
3rd when you fix file then ran back the stock firmware which will fix bootloader
then go back install twrp and install custom rom with root, remember 910t, 910t3 comes with unlocked bootloaders no need to unlock them
Click to expand...
Click to collapse
ok guys so my dad has bricked his nokia .8.. i managed to get Twrp working again. and that's about it.. the bootloader is unlocked but i cant can't unlock "bootloader critical" it says something like " (remote command not allowed)" when i check the device info it says bootloader is unlocked but bootloader critical is not.. iv tried flashing via the ost but it says i need to unlock the critical bootloader..
another problem is that i cant flash in twrp. it says invalid zip file or something...
has anyone got a Twrp Backup they could upload so i can try and get this thing working again? or a zip i can flash via twrp?
cheers.
Did you do "fastboot flash unlock <path to unlock.key>" before trying to execute "fastboot oem unlock_critical"?
Did you maybe have an unlock key that was generated through the unofficial unlock (every build before august 2018) and are now on a newer build that supports only the official unlock?
If you can't manage to unlock the bootloader to critical, get some stock boot image (I have some at https://bit.ly/nokia-nb1), flash that to your active boot partition in fastboot (overwrite TWRP with it), then boot into stock recovery and sideload a full OTA package (which will restore all partitions that might be corrupted). All 1.5 GB files you can see in the OTA folder at the link I posted are full OTAs and will work.
ok so just an update i managed to get a rom on there, i found the right key and did the unlock all over again.. all booted ok, problem now is that i have no signal... i cant send any mssgs or phone calls. i tired to update the smsc. via this *#*#4636#*#*. and going phone info etc, but it says update error, iv also tried the encoded number for ee, but still says update error. i can put the sim card into another phone and it will send messages etc, i did read that i could update the smsc on a diffrent phone then put it back into the nokia and it will work, but it did not for me...
again there was another video showing how to fix this via backing up the firmware folder on rom then replacing with the one that dose not work . but ... i dont have a rom that works lol . iv also tried to install diffrent roms or systems and still the same problem.. i use the NOST tool. to update the firmware
any advice????
also this is his account hence a diffrent account name lol
cheers