Hello all Masters
I own HTC desire C i first did everything correct
with this thread http://forum.xda-developers.com/show....php?t=2275761
but there was no google apps and all
so i retried the same procedure with GAAP (Please forgive me i dnt remember)
and got my phone all DEAD
I have given HTC centre they says motherboard is dead u have to spent 5700 rs for the same.
as i can not bare that much money.. hard working guy..
Now
with details of error
****UNLOCKED*****
GOLFU PVT SHIP S-ON RL
HBOOT-1.31.0000
RADIO-1.10.98.15
eMMC-boot
Jul 12 2012,15:44:30
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.31.0000
(bootloader) version-baseband: 1.10.98.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.00.720.2
(bootloader) serialno: removed
(bootloader) imei: Removed
(bootloader) product: golfu
(bootloader) platform: HBOOT-7225A
(bootloader) modelid: PL0110000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4204mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e118df77
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
I have tried everything as its S-ON so can not got recovery mode
C:\android-sdk\sdk\platform-tools>adb push NaMeLeSsR0m_v7.o.0_HtCDeSiReC.zip /sd
card/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android-sdk\sdk\platform-tools>adb devices
List of devices attached
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (4888 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 0.932s
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (4888 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 0.932s
Nothing works for me please help
Good thing is that now adb recognise my device and i have put my memory card into samsung phone and with
the help of gold card helper i have made gold card and patched it
now i am using
RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_ 32U_5_11_05_27_release_159811_signed
i renamed rom.zip to PB99IMG.zip and kept it in sd card
now since the mobile can not do anything so i used the
RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_ 32U_5_11_05_27_release_159811_signed
clicked on next it sayd battery is less than 30%
Guys M i on right path ????
although i m not too much experienced but i would suggest you try Cyanogenmod10
i used rom files from this http://forum.xda-developers.com/showthread.php?t=2265060
i used """BUILD#3: ( WiFi Fixed ) http://forum.xda-developers.com/show...&postcount=370""""
Right idea but TOTALLY the wrong files!
Why use a PBxxxx.zip that has nothing to do with your model phone?
(the correct info is in the data you posted about HBOOT!)
Why are you flashing an RUU for bravo? This isn't even related to the Desire C in any way!
I would suggest before you brick your phone (which hopefully won't happen if you're not S-OFF or Dev Unlocked so security will stop you!) to read up in the forums on the problem you have and possible work-around/solution/s.
Most, if not all, are or have related solutions or work-arounds.
Bashing away at my HTC Desire C
Related
Hi,
Yesterday I got an HTC One that I won from HTC directly (I work in the mobile industry).
The phone was already S-OFF when I got it from HTC, but for some reason I can't seem to flash any recoverys.
This is what I get when I try to flash the recovery:
sending 'recovery' (7270 KB)...
OKAY [ 1.140s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.174s
Any tips?
Dezzorex said:
Hi,
Yesterday I got an HTC One that I won from HTC directly (I work in the mobile industry).
The phone was already S-OFF when I got it from HTC, but for some reason I can't seem to flash any recoverys.
This is what I get when I try to flash the recovery:
sending 'recovery' (7270 KB)...
OKAY [ 1.140s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.174s
Any tips?
Click to expand...
Click to collapse
Have you unlocked bootloader and got cmw
Hi
Greetings,
Give us the bootloader info
This happens
1 locked bootloader
2 corrupt recovery IMG
If your unlocked,
Download all in one toolkit ( search in development sectors) and follow that guide
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
Give us the bootloader info
This happens
1 locked bootloader
2 corrupt recovery IMG
If your unlocked,
Download all in one toolkit ( search in development sectors) and follow that guide
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
This is what I get from getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3872mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.067s
Okay - Don't want to say NOOB mistake but, failure to follow direction - YES. In any case I NEED HELP!!! Like everyone else, sold my phone and attempted to put it back to stock.
Changes made - Changed to Google Edition from AT&T.
- Rooted Phone - S-OFF - Changed CID to GOOGL001 - flashed GE RUU.zip -- Enough said
Changes made to go back to stock
- Changed CID back to CWS__001 -- Turned S-On ** First mistake -- Locked bootloader -- attempted to flash ATTRUU
- Went to flash cyanogenmod just to have a rom and accidentally FORMATTED in TWRP -- 2nd mistake
I have also tried every RUU that might have an inkling of success but all i get is the 12 signature verify fail
I have tried everything twice. But with out S-OFF i think i'm dead in the water.
I tried - flashing hboot1.44 (modifing android-info) and get error
c:\androidsdk\sdk\platform-tools>fastboot flash zip hboot144.zip
target reported max download size of 1526722560 bytes
sending 'zip' (508 KB)...
OKAY [ 0.230s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.279s
** I have tried RUU.exe's but nothing will go because of the CID/HBOOT mismatch
Here is what I have
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35GW903487
(bootloader) imei: 354439055133427
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 6.940s
** If i could just flash an hboot - I could get an RUU working but again I need S-OFF.
- Also when I try to flash cyanogenmod from recovery, it says Unable to mount system, data, can't mount **** and I assume because recovery reformatted them and the correct file systems are not in place.
FML!!! PLEASE HELP
Read Vomers great post, and follow the instructions very carefully
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Also remove your imei number from your post
Sent from my HTC One using xda app-developers app
Guys, absolute noob here, so please bear with me.
I have a European HTC One with HTC Sense, long time ago I loaded Cyanogen on it.
now I want to sell it, so I am trying to put Sense back.
first, I locked the phone with ./Fastboot oem Lock.
I downloaded the RUU for the stock, I got a ZIP instead of an exe because I do not have access to a windows machine (please dont tell me to create a VM because my Mac for some reason doesnt deal well with vmware/bootcamp. so I have to do this on OSX).
this is the RUU name:
RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted
so this is what I did:
fastboot oem rebootRUU
fastboot flash zip RUU.zip (I had renamed the zip file for short).
this is the output:
ahmads-mac-mini:android ahmadshaheen$ ./fastboot flash zip RUU.zip
sending 'zip' (1010240 KB)...
OKAY [ 42.967s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 143.829s
I tried doing it more than ten times, rebooted the mac, the phone, no result, same error. I thought this error has to do with the version, the rom version is exactly the same as the mainver on the phone.
here's a getvar all output:
ahmads-mac-mini:android ahmadshaheen$ ./fastboot getvar mainver
mainver: 1.29.401.16
finished. total time: 3.382s
ahmads-mac-mini:android ahmadshaheen$ ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4049mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
I am pretty much stuck in fastboot, I cant get into recovery or bootloader or anything, just fastboot.
I hope I have not bricked the phone !
Hi,
First of all, edit your post and remove imei numbers from:
(bootloader) imei:
And
(bootloader) serialno:
Now, try this:
http://www.htc1guru.com/downloads/stock-rom-downloads/
But you must do s-off to totally revert back to stock without tempered flags or relocked.
Hello all.
Target
Install the google edition rom for my HTC one M7 (Was originally a SENSE one). If not possible, install Sense stock rom.
Problem
* Unable to install any not cyanogen roms.
* Unable to S-OFF (not mandatory if not required).
Device info
Code:
-> % sudo fastboot getvar all [21:34:02] [ruby-2.1.2]
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W903198
(bootloader) imei: myImey
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4313mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 13.410s
Step to now
* Unlocked
* Tampered
* Recovery: ClockworkMod
Roms installed
* CM 11
* Back to CM 10.1 , some topics said revone will work. But no way.
S-OFF tries
Tried to S-OFF, but no success
* revone reboots device without any error ( no matter the android version)
* runrunner just didn't work
* SunShine claims for a stock, but unable to flash with a RUU:
RUU reinstall tries
RUU name: RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
RUU source: htc1guru (since I'm a newb here, I can't post direct url)
md5sum is ok on computer disk
Flash process followed
Code:
-> % sudo fastboot oem lock [21:30:51] [ruby-2.1.2]
...
(bootloader) Lock successfully...
OKAY [ 0.024s]
finished. total time: 0.024s
=> Ok after reboot, says "RELOCKED"
-> % sudo fastboot oem rebootRUU [21:31:14] [ruby-2.1.2]
...
(bootloader) Start Verify: 3
OKAY [ 0.037s]
finished. total time: 0.037s
=> OK, black screen with HTC logo
-> % sudo fastboot erase cache [21:31:41] [ruby-2.1.2]
erasing 'cache'...
OKAY [ 0.378s]
finished. total time: 0.378s
-> % sudo fastboot flash zip RUU.zip [21:31:45] [ruby-2.1.2]
sending 'zip' (1010240 KB)...
OKAY [ 61.263s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 162.160s
I don't know what to do to fix this strange issue.
Thank you for reading all my report, and helping me if you have an idea .
isildur37 said:
Hello all.
Target
Install the google edition rom for my HTC one M7 (Was originally a SENSE one). If not possible, install Sense stock rom.
Problem
* Unable to install any not cyanogen roms.
* Unable to S-OFF (not mandatory if not required).
Device info
Code:
-> % sudo fastboot getvar all [21:34:02] [ruby-2.1.2]
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: [COLOR="Red"]PVT SHIP S-ON[/COLOR]
(bootloader) serialno: ..............
(bootloader) imei: myImey
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4313mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 13.410s
Step to now
* Unlocked
* Tampered
* Recovery: ClockworkMod
Roms installed
* CM 11
* Back to CM 10.1 , some topics said revone will work. But no way.
S-OFF tries
Tried to S-OFF, but no success
* revone reboots device without any error ( no matter the android version)
* runrunner just didn't work
* SunShine claims for a stock, but unable to flash with a RUU:
RUU reinstall tries
RUU name: RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
-> % sudo fastboot oem lock << Good
...
(bootloader) Lock successfully...
OKAY [ 0.024s]
finished. total time: 0.024s
=> Ok after reboot, says "RELOCKED"
FAILED (remote: 12 signature verify fail)
finished. total time: 162.160s << Your not S-off
[/CODE]
I don't know what to do to fix this strange issue.
Thank you for reading all my report, and helping me if you have an idea .
Click to expand...
Click to collapse
You need a true RUU not a decrypted one your not s-off
Try this one http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_316789_signed.zip
flash it with
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip <yes 2 times>
fastboot reboot
Your idea worked great, thank you!
Then I was able to S-OFF, change my CID install the Google edition ROM.
Big thanks
isildur37 said:
Your idea worked great, thank you!
Then I was able to S-OFF, change my CID install the Google edition ROM.
Big thanks
Click to expand...
Click to collapse
How did you do it? Sunshine?
jcneivar said:
How did you do it? Sunshine?
Click to expand...
Click to collapse
Rumrunner works on hboot 1.44 - 1.54 - 1.55 for free
Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ÒÀü«/ë¥-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Have you tried to flash stock recovery or RUU?
JB_ said:
Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ÒÀü«/ë¥-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Click to expand...
Click to collapse
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
alray said:
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
Click to expand...
Click to collapse
Well as I want to remember it I don't think I have flashed a rom yet, I never got that far I just tried to flash twrp 2.8.4.0.
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
JIMSHERIKO said:
Have you tried to flash stock recovery or RUU?
Click to expand...
Click to collapse
Well if I understand it right when I try to flash a RUU it just says unknown modelid and I think because it's corrupted or something. :/
JB_ said:
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
Click to expand...
Click to collapse
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
alray said:
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
Click to expand...
Click to collapse
Ah so i need to get TWRP up and running for adb to work then.
Well looks like i got my awnser then. Thank you for your time!